<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<?xml-stylesheet type="text/css" href="/css/xml.cad8b34c5c205e166e21ff13bc54144feeb0fe76ed4c8982c8d240291824cf75.css"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Blackfyre’s Blog</title>
    <link>https://blackfyre.ninja/blog/</link>
    <description>Notes on Go, architecture, infrastructure and tooling by Miklós Galicz.</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Sat, 14 Oct 2023 07:15:40 +0200</lastBuildDate>
    <atom:link href="https://blackfyre.ninja/blog/index.xml" rel="self" type="application/rss&#43;xml" />
    <item>
      <title>Using the native dialog with HTMX</title>
      <link>https://blackfyre.ninja/blog/using-the-native-dialog-with-htmx/</link>
      <pubDate>Sat, 14 Oct 2023 07:15:40 +0200</pubDate>
      <guid>https://blackfyre.ninja/blog/using-the-native-dialog-with-htmx/</guid>
      <description>An empty &lt;dialog&gt;, a fragment from the server and an HX-Trigger header: modal windows with htmx and no modal library.</description>
      <content:encoded>&lt;p&gt;Recently I&amp;rsquo;ve found out about htmx and immediately fell in love with the concept of ditching frontend frameworks for ~90% of the use cases I deal with on the regular.&#xA;Alas, there are things we still need additional help with, but thankfully htmx is very helpful in that regard as it&amp;rsquo;s extensible and works well with other scripts and even with frameworks.&lt;/p&gt;&#xA;&lt;p&gt;My other fixation is using browser native features as much as possible (they are there for a reason…). While this is not something shared by UI designers, it&amp;rsquo;s more often easier to have the design adjusted than finding a library that supports both the design and business requirements when there&amp;rsquo;s a crunch.&lt;/p&gt;</content:encoded>
    </item>
    <item>
      <title>Adding a Vuex store to your Laravel Nova Tool</title>
      <link>https://blackfyre.ninja/blog/adding-a-vuex-store-to-your-laravel-nova-tool/</link>
      <pubDate>Tue, 13 Nov 2018 07:32:02 +0100</pubDate>
      <guid>https://blackfyre.ninja/blog/adding-a-vuex-store-to-your-laravel-nova-tool/</guid>
      <description>Nova owns the root Vue instance, so a tool can&#39;t hand it a store. Create one in Nova.booting, keep it on the Nova object and read it from your components.</description>
      <content:encoded>&lt;p&gt;Since Laravel Nova is the fresh kid on the block, the community is still working out how best to solve things and settle on best practices. One of the first questions I ran into: how do you give a custom tool its own Vuex store?&lt;/p&gt;&#xA;&lt;p&gt;The usual answer, passing &lt;code&gt;store&lt;/code&gt; to &lt;code&gt;new Vue()&lt;/code&gt;, doesn&amp;rsquo;t work here. Nova creates the root Vue instance itself, and your tool only gets a say during &lt;code&gt;Nova.booting&lt;/code&gt;. So &lt;code&gt;this.$store&lt;/code&gt; in your components is not yours to set.&lt;/p&gt;</content:encoded>
    </item>
  </channel>
</rss>
