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. 

Menu

Half way in to creating a submenu for the Aotearoa program, and I've totally forgotten about console windows and their attributes. Like, having a do while loop to make sure someone doesn't crash the program and all that random blubber. Gosh, if I had more time, I would so convert it into a GUI. I don't think i have the time though.

And best, it already reads/writes from a file, and uses a class. I just need to make the things inside private.

LOL

ROFL, I cannot get over how stupid my programming is! Haha, it's actually pretty hilarious...I have throwsIOException on every single method header (instead of try catches) and for some reason, I'm duplication the Accommodation array twice, and sending copies from method to method. But like....8 out of 10 methods use the array, there's no point of sending back and forth.

Sending and Receiving Between Methods

I'm actually so confused about what the heck I programmed back then. Perhaps it was the methods assignment, cause I'm just so randomly sending arrays between methods - but because every single method has to access it, it just makes sense to put it into the in the class.

I'm starting to be convinced that it was the methods assignment and I was finding ways to check things on the rubric, but that's the stupidest way to program!

Rewrite

Okay, well..even though we aren't going to Aotearoa for the school trip, for the awesomeness of the country and the funness of the program, I might as well re-edit it.

I'm going to add sorting in it:

• Date 
• Locations (Alphabetical) 
• Price
• Type of Accommodation (All Holiday Parks together; all hotels together (as if we'd be staying in a hotel, psft!)) 
• Name of Accommodation (Alphabetical) 

Sorting the date: Use the selection sort, because it works the fastest by cutting the entire list in half every time. And after touching one of them, they can ignore it. 

Sorting the location (alphabetical): Perhaps using the bubble sort will make it most efficient. 

Sorting the price: Use the selection sort as it also works the fastest by cutting the list of who-knows-how-many-days-we-are-going in half. 

Sorting by Type of Accommodation: Okay, that one is quite a bit harder. Hmm..gotta think about that. 

Name of Accommodation (Alphabetical): Whichever one that has the lowest unary operator number.