Quote:
|
Originally Posted by PandaMoOo Yes, its meant to be for classes you want to take FIRST. The short answer is: it only matters if my system can find over 300 schedules and then it stops looking. It uses the classes in the beginning of the list to find those 300 schedules, it then sorts those according to the sorting parameters.
Wonderful suggestion! I would be willing to implement it under 2 conditions:
1) I could design an interface that is not too hard to use, thus people would use it. (I would even have it store peoples information in a user account, thats an easy one.)
2) (The BIGGEST PITFALL) I need a way to automate the system, a place to get all the needed information. Is there any non-PDF based list of classes that I could pull from for all majors? With different majors for different years... it still could be done, but I can not reasonably enter all the information myself. I need a way to automatically grab the classes required, and of course the prereqs/coreqs for those classes.
WONDERFUL IDEA! I know a lot of the information is hidden within PDFs... I'm not sure if I can get perl to dig through it good enough... and if i could automate the process. I'll look into how much work it'd be... THANKS! |
I can help you out with atleast some I guess... I already had made a flowchard for my major because the one the department provides COMPLETELY SUCKS!!!!
Yeah... it will be VERY TEDIOUS!!! especially for one person taking care of ALL the majors... If you were to just have 1 person from each major help you out here... then 1/2 the work willl be done.
I have the MFE one if u want... hehe. I can do the IE and ME one also.
But remember... user interfaces are a high priority!!! Sadly, ppl care more for how a thing looks than how it functions. So dare I say having a "flash" enabled interface will blow ppl away... but then u have the problem of user requirements... ugh!!! HOW DO U DO THIS!!! :P