<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Don't Use FXML on PragmaticCoding</title><link>http://localhost:1313/javafx/techniques/nofxml/</link><description>Recent content in Don't Use FXML 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, 22 Jul 2025 12:00:00 -0500</lastBuildDate><atom:link href="http://localhost:1313/javafx/techniques/nofxml/index.xml" rel="self" type="application/rss+xml"/><item><title>Should You Use FXML?</title><link>http://localhost:1313/javafx/techniques/nofxml/fxml-or-not/</link><pubDate>Mon, 10 Mar 2025 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/nofxml/fxml-or-not/</guid><description>FXML. There are all kinds of claims about its value, but are they right?</description></item><item><title>FXML is NOT Model-View-Controller</title><link>http://localhost:1313/javafx/techniques/nofxml/fxml_isnt_mvc/</link><pubDate>Mon, 20 Feb 2023 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/nofxml/fxml_isnt_mvc/</guid><description>Lots of programmers and websites think that FXML instantly gives them a step up on Model-View-Controller, with the FXML File yielding the View and the FXML Controller acting as the Controller. We&amp;rsquo;ll look at why this isn&amp;rsquo;t correct, and how you should implement FXML in the context of MVC.</description></item><item><title>How to Write a JavaFX Screen without FXML &amp; Scene Builder</title><link>http://localhost:1313/javafx/techniques/nofxml/layouts-without-fxml/</link><pubDate>Tue, 24 Aug 2021 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/nofxml/layouts-without-fxml/</guid><description>I&amp;rsquo;ve always advised that Scene Builder and FXML are a waste of time, and that you should just write your screens in Java code.&lt;br&gt; It&amp;rsquo;s easier to build, it&amp;rsquo;s easier to customize, easier to maintain, and much, much easier to do really sophisticated things. But how do you start?</description></item><item><title>Converting FXML to Code</title><link>http://localhost:1313/javafx/techniques/nofxml/fxml-to-code/</link><pubDate>Tue, 22 Jul 2025 12:00:00 -0500</pubDate><author>nuno@n9o.xyz (Blowfish)</author><guid>http://localhost:1313/javafx/techniques/nofxml/fxml-to-code/</guid><description>I&amp;rsquo;ve talked a lot about how coded layouts are better than FXML. In this article we take a fairly large FXML based layout which is part of a larger project, convert it to code, and implement a framework using a Reactive design. Is the final result better than FXML? See for yourself.</description></item></channel></rss>