AW/BW/WW

I'm so confused..for some reason, I'm outlining like what documentation I wrote before coding, while coding and after coding (afterthoughts) in the documentation, but it makes no sense, lol. I'm not even sure what I'm trying to accomplish. It was probably a rubric requirement back then, and then I'm looking at it now and it looks so strange..

It definitely does look quite strange.

The little things on the top of each box are comments and questions that I have to ask Ryk. Like external documentation - one? two? Also, what does he mean by decomposing a problem into models, classes, or abstract data types, using and object oriented design methodology...like what is a model? Ah well, those questions, I guess can wait. 

Ah! I do have one contemplation...

If I rewrite my program in a gooey, it's going to take 10 x the time it would normally take, but look ten times uglier. If I just leave the program as is, and add sorting, it won't take as long. But even if it was in a gooey format, I don't know to format it..okay, well, I guess I do. I'll have to plan it out and weigh the positives/negatives first. 

Perhaps something like this? 

But on the other hand, converting this to a gooey is going to take so much time and effort (that I'm not sure I have). It would definitely be a lot more user-friendly that way. Perhaps...but the time required to make that into a gooey, plus learning how to make a menu bar, and then finding the sort is a mini nightmare within itself. AGH.