We recently got together and discussed the algorithm we are going to use for the schedule generator. We've come up with a way so that it performs better than brute force, but still gives us all of the permutations of the schedule that we want. It will take in a list of classes, the algorithm will then create a list for each class of each of the class's sections. We will then step through the list of lists and compare each section to the other class's sections. On the comparison of the first two section lists, if the sections fit, another list of the possible schedule will be created. We then use the new schedule lists to compare with the other classes. The growth of the # of lists is the number of current schedule lists * the number of classes in the next section list. If there is a class that does not have a section that fits with any of the possible schedule lists, the algorithm will short circuit and declare that there are no possible schedules with the selected set of classes.

Our client meeting with Dave this past week was very helpful. His urgency on us implementing our final feature (the schedule generator) put our time frame in perspective. However, I feel that we should be able to implement the feature in time for the next demo.

We recently had our meeting for filling out the business model form to help solidify what information we are going to present for the pitch. It is really amazing at how something with so little can eek out so much thought of what would actually have to be done to create a fleshed out business model. We, of course, did not fill out everything since we only have 4-5 minutes to actually present the information during the pitch. It was interesting that there was a lot of overlap in the topics within each box. As we were filling out the information, we would get to another whole box that would be there to flesh out a single aspect of a previous box.

VisualScheduler is looking good. The static pages are done, the backend is essentially complete, and the Scheduling page is making wonderful progress for the the pitch demo.

Finally finished the html frontpage for the web app. It looks pretty bare at the moment, but it's at least ready to be polished to everyone's liking. Time to start on the about, help, and contact pages.

Hell f*****g yeah! Intellij fixed my project problems (though it took me a few hours to figure out how to set everything up). I can finally code without having to deal with janky hacks around the problems (still don't know why they even existed) and can now jump on making our html pages with piece of mind.

Since I've been having severe issues with our project on eclipse, I have been looking into Intellij by the recommendation of Zach Harding. I really hope that it is as good as it claims to be and will resolve my issues.