<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
	<channel>
		<title>Almost...</title>
		<link>/blogentry/196601</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/196601" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Almost...</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Almost...</title>
			<link>/blogentry/196601</link>
			<guid isPermaLink="true">/blogentry/196601</guid>
			<pubDate>Sun, 11 Jan 2026 05:41:41 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>The GUI app is running! All functions are operational without crashing, and the data displays cleanly!<br /><br />Somehow I lost my sorting, and have to fix followers to show counts, but it ran on multiple games with a clean exit!<br /><br />I am way ahead of where I thought I would be at this point... but not at the finish line just yet.<br /><br />Serious progress has been made! The updater works flawlessly, and each of the 2 main scripts executes without syntax errors... now the tweaking of output is the next level... have to get the output to match that of the original scripts.<br /><br />So the road map is as follows...<br /><br />1. Fix the data output to restore sorting and putting the data where it belongs on the output screens<br /><br />2. Make it look pretty. This includes making images and icons for branding .<br /><br />3. Write the technical documentation for the windows version.<br /><br />4. Get it 100% polished<br /><br />5. Start the android implementation.<br /><br />I know it sounds ultra simplistic, but this is a huge step for my coding journey... I am starting to truly understand how separating layers into a framework is done, and why. Writing the game meta data file that connects the user interface to the back end scripts was an involved process... that it mostly works is crazy!<br /><br />End to end run with a clean shutdown! The data output should not be too hard to fix... i hope.<br /><br />One immediate benefit is that I am getting much better at interpreting python trace errors back to their source AND figure out what went wrong... so much easier when you try things that are being processed and catch errors with descriptive messages.<br /><br />This is so much more satisfying than following a tutorial, feels like real learning!<br /><br />What a coding day!... &#x5b;&#xa0;<a href="/blogentry/196601">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/196601</wfw:comment>
		</item>
	</channel>
</rss>

