Breaking up the side by side output from the universal classifier script into per column printouts.

Why?

Starting the Kivy app development can begin!

The basic process is to get the data to print out per column, as these prints will be redirected to a kivy widget.

The test is a giant launch where it will be called to process all 17 games in sequence. The only thing that changes is the low and high ball arguments and the name of the csv file to process. This is the chance to permanently suppress any possible errors. This has to be 100% universal and working before it starts populating a kivy grid layout.

The updater works as far as running and providing 100% correct data to all of the csv files. They just need the prints removed and the percentages entered for the progress meter.

This should make the process relatively quick to get some grid layouts together.

Some of the development will take longer, such as being able to produce graphs and getting the ball graphics sorted out, but there is a general idea of how it will look.

That "look" was done on a sheet of paper. No wireframe development needed.

My goal is to have the windows version done by the end of the year. 

First it must be functional, then I can tweak the look and feel of the app BEFORE even thinking about porting to Android.

Since it is not for sale or redistribution, I can borrow graphics straight off of the PA lottery site... that will be a huge time saver!

I do not think it would be too difficult to incorporate the follower scrips for any of the games, I already converted that script to a by-column output that will be easy to place the output into kivy widgets side by side. Adding this script makes it more of a framework than a single solution, and that was part of the overall vision for the project.

The core systems (followers and classification) have not yet proved effective in converting picks to winners on a regular basis, but each HAS picked at least 1 straight hit this year. Have to start somewhere, right?

Remember, the overall goal here is not picking winners, it is creating a multi platform (windows and android) application from a single code base AND learning graphical user interface coding. On that front, I predict the same path as learning to script... encounter problems, solve them, refactor... in a loop until it works as intended. THEN I can go back to trying to win something. Also a key to this process will be learning how to compose documentation.

On that front I created a project folder called "CHANCE" and enabled git version control on the folder. This way, new features can be added as branches and rolled into the master branch only when 100% functional. The next step will be to do the activities above and start populating the project folder with the finished scripts and clean copies of all 17 csv files. Then a graphics folder will be added with everything needed for button images for each game and the number images. Sticking to Android patterns, that will be the "img" folder.

Gonna be a busy few weeks!