Hello,
I started this project because I was playing Chapter Master and more than a bit bummed out that development had stopped (UNLOAD ALL BUTTON FFS). It seemed like a simple enough project so I decided to start on it, expecting the bare bones project would take me a day. It took me closer to a week to get the barest essentials down.
I do not want to be associated with this project at all in person (I'm using Tor to access this) due to previous difficulties experienced by previous developers. So onto the next topic...
Source CodeIt was never my intention to spend more than a day on it and my goal was to simply create the groundwork. Thus, I originally intended to release the source. However, since I've spent more time than I expected on it, I've created a couple of nifty functions I'd like to C+P. I like reusing functions (I've reused a couple of old functions for this already) and I will be reusing significant portions of my code in the future. My code is a bit distinct given that I'm using this as a learning project. So no, I will not be releasing my source code.
I will however be amenable to offering a "recipe" for it, written in plain English talking about how I implemented all of the parts (i.e. what classes I have, who owns what, a general sense of how the thing works). I'm hurting as well; due to the nature of this project, I can't grow my code portfolio with this.
If someone with more balls wants to follow my "recipe", and/or writes their own (high quality, clean, self-documenting) code, I'd be glad to step back and help contribute to that project instead. If someone's interested in taking this up and has coding abilities in an OOP language, email/PM/post ASAP and I'll drop coding and start writing.
Update ScheduleWhenever I feel like it (Anything less than once a week is probably bad for my health and sanity). Burnout is always a risk. I hope to remain motivated enough to tell you I'm quitting when I do decide to quit.
Blog planned. In the meantime,
here's an update which adds equipment. Don't expect any more updates this soon/work done this fast; it's probably best for my health/sanity/cleanliness of code that I work slower on this. I promise to myself that I won't include an update within the next week. Because this was a rush job and because I originally intended to release it, the code is both messier and convoluted than planned. Cleaning is underway.
Email me for questions and I'll do my best to answer them.