<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Layout Techniques on PragmaticCoding</title><link>http://localhost:1313/javafx/techniques/layouts/</link><description>Recent content in Layout Techniques on PragmaticCoding</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>nuno@n9o.xyz (Blowfish)</managingEditor><webMaster>nuno@n9o.xyz (Blowfish)</webMaster><copyright>© 2026 Blowfish</copyright><lastBuildDate>Tue, 24 May 2022 12:00:00 -0500</lastBuildDate><atom:link href="http://localhost:1313/javafx/techniques/layouts/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Swap Scenes Properly</title><link>http://localhost:1313/javafx/techniques/swap-scenes/</link><pubDate>Tue, 24 May 2022 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/swap-scenes/</guid><description>Taking a look at the three most common design patterns for building systems with user interfaces. How are they different? which one is best? Is there anything better?</description></item><item><title>Building Views - The "Set It and Forget It" Approach</title><link>http://localhost:1313/javafx/techniques/setitforgetit/</link><pubDate>Mon, 14 Mar 2022 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/setitforgetit/</guid><description>The best way to structure an application is to separate the presentation of your data from the logic of your application. That can be hard to do. But not if you take an approach where you configure your screen elements, put them in the layout and then discard any reference to them.</description></item></channel></rss>