<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Desktop on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/desktop/</link>
    <description>Recent content in Desktop on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/desktop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Qt vs wxWidgets vs FLTK in 2026: Choosing a C&#43;&#43; GUI Framework</title>
      <link>https://www.pistack.xyz/posts/2026-09-06-cpp-gui-frameworks-qt-wxwidgets-fltk-comparison/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-06-cpp-gui-frameworks-qt-wxwidgets-fltk-comparison/</guid>
      <description>&lt;p&gt;Pick up any C++ desktop application and odds are its UI was built with one of three frameworks. Qt powers KDE Plasma, VLC, and countless embedded dashboards; wxWidgets sits underneath Audacity and KiCad with controls that look exactly like the operating system&amp;rsquo;s own; FLTK has been quietly shipping tiny, fast utilities since 1998. Yet choosing between them in 2026 is harder than ever, because the real differences are not feature checklists — they are &lt;strong&gt;licensing obligations, native look versus drawn widgets, and how much of your binary you are willing to spend on chrome&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
