<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Refactoring on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/refactoring/</link>
		<description>Recent content in Refactoring on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/refactoring/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Designing Reusable Config Screens: From Vertical Labels to Table Layout</title>
				<link>https://phosphorbbs.net/blog/designing-reusable-config-screens/</link>
				<pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/designing-reusable-config-screens/</guid>
				<description>&lt;p&gt;Every config screen in Phosphor BBS used to be a snowflake. SystemConfigScreen had its own layout. AiConfigScreen had its own layout. They looked different, behaved differently, and shared no code. Adding a new settings screen meant copying one of them, stripping out what you didn&amp;rsquo;t need, and writing the rest from scratch.&lt;/p&gt;&#xA;&lt;p&gt;This is the story of how we fixed that — extracting a reusable &lt;code&gt;TableConfigScreen&lt;/code&gt; parent class and converting every config screen to the same table-based layout, killing about 150 lines of boilerplate in the process.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
