<?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>Today&#x27;s coding plan</title>
		<link>/blogentry/195187</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/195187" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Today&#x27;s coding plan</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Today&#x27;s coding plan</title>
			<link>/blogentry/195187</link>
			<guid isPermaLink="true">/blogentry/195187</guid>
			<pubDate>Mon, 20 Oct 2025 13:07:32 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>For today, I will take the successful update to the Match 6 script, which was the multi level sort from the pick N script, and apply it to the Cash 4 Life script.<br /><br />Also, after watching a few weeks go by, I am discontinuing the practice of cutting the head of the draw samples to remove the window... that means the scripts will no longer remove 21 draws from the sample in pick N, 28 draws from Match 6 or 30 draws from Cash 4 Life. It was an idea that did not yield any positive (or negative) result.<br /><br />Over time, I will be moving forward with a GUI version for these scripts, with the ultimate goal of having all games in one program. Variables entered from a settings page rather than direct script editing. I believe I have followed the best path by making sure all functions for all games work and display the desired information. The GUI transform will be a puzzle put together with verified working pieces! This will also allow for graphs to be incorporated without running a different script.<br /><br />I still have to figure out how to update the draw histories by scraping the data from the PA website (The RSS feed does not provide reliable or consistent data). That consists of automating what I do manually... so I already know the steps in the process...<br /><br />But then I will have a single desktop app that can handle everything I do with the lottery. It will be another chance to apply industry best practices and branch out into another new area of Python coding for me. One of the design challenges I have already started exploring is the reading of the input file to create a dynamic layout, just like the pick N script can auto configure side by side output for pick2 through pick5.<br /><br />Once that is done, then the ultimate goal can be started... a mobile app! Everything in one place for calculations on the fly without needing all the time currently required to set things up.<br /><br />But for today, I am sticking with the Cash 4 Life update... one step at a time...... &#x5b;&#xa0;<a href="/blogentry/195187">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/195187</wfw:comment>
		</item>
	</channel>
</rss>

