I have a whole written plan laid out, detailing EVERY menu this program will have, how the code will be structured in terms of where these menu's code's exists, and a daily plan for how much I should aim to add in one day. Although, the first steps will be the longest because that's designing the editor and the basic trigger functions.

Yeah, I've got my sprite sheets ready save for one or two buttons. Aside from that, my programs use graphic drawn fonts so I can easily add them to sprites and change their color to exact RGB values, so I write a function to draw text from data in an array, and the design part is mostly done. Of course, that's not accounting for the submenus which are drawn only when needed.

Just finished recording a daily-ish plan for BitByte MML, now that I think of it, I should be able to finish in around one month. I kind of crammed everything in the 'schedule' though - yeah, with the amount of stuff to do (especially for day one) 12 days is probably not enough!

In case my inaccuracy makes that difficult, it ACTUALLY started with "I still haven't added much"

Check my play journal. In the comments for a post beginning with "Still haven't done much" I explained many of my goals :D

Oops, that's the key for a deleted version. The new key is NK4P4EBD. (I updated it twice so this is 1.0.2)

Yes, it's a game I made a while ago. One of the main reasons I'm making BitByte MML is so I'll have a personalized program with which to make music for it, which POLYGON presently lacks! The key is B2KXCW3E.

On a different-ish topic from my previous post, I DID successfully make a test program that records MML from notes pressed on a keyboard, so that should be helpful when I get to the 'virtual MML controller' part of BitByte MML!

Well, it's a bigger project than POLYGON and that was made through slow progress over nearly (probably more than) a year. I'm going to try to put in more effort toward it whenever I can until it's usable!

Ah, geez. Code, not coad.

Now, with SmileBASIC, it's even easier. I would suggest loading the coad for some samples and pressing the question mark button on the top-right corner of the keyboard to see what the commands in the samples are doing, and what the syntaxes for those commands are. Then try using those same commands in your own way.

Well, there is certainly no way to summarize how to program in BASIC in only a paragraph or two. How I learned was through looking at samples, figuring out how their code works, and making small programs of my own using the commands I wanted to learn. After referencing those commands to the manual several times I got the hang of that command.

Besides, I've got a plan laid out and I'm feeling motivated once again. It should take only up to two months to get done!

Well, I didn't even finish the CHANNEL OPTIONS menu or get to actual music construction, so I don't have to go back too far. Besides, remaking it should improve the user experience and make it run faster :D

Oops, I forgot a 'G' in there!

Well, it's been a while, but I'm coming back to this. I'm starting to get really dissatisfied with some of the programmin and code structure, though, so I believe that a restart on this project is in order...

Yeah, like I said I'll use PRG slots 1-3. The program will of course create them as you use it. And of course I have to consider the upload memory limit! I figure DATA would be the most efficient so the program can search through the information quickly.

I hope its not too confusing. I figure it should work while still allowing the program to run relatively fast. Any thoughts?