Aaron Cayard-Roberts
open source
9-8-00

Login.cgi
-starts out with a bunch of ifs that decide if the users is
logging in or use the tools that a non-logged user can use. After
that follows all the functions with html that show different 
screens, login screen, logout screen, picks if person logging in 
is a student or professor and what links to load accordingly, has 
the function with the html for the how to contact us (DBA group),
has the function with the html for the news/history of webdb.

Course_search.cgi
-begins with many elsifs that decide what button were picked to 
to do the search on…the course_search function has a long string
of ifs that check what fields were picked to search on.

The registrar tool just lets the registrar enter in lots of
information.

	There is lots of code, most of it is fairly straight
forward, with the files being self descriptive.  Not knowing cgi
I can still get an idea about what's going on and I get the general
idea about what's what.  From what I can tell it seems to be
written kind of choppy and it would be nice if there was some
more comments on stuff.  The architecture is client server,
serving the users while being a client to the physical 
database.  Most of the users end things that I had to complain  
about I found out where fix in the last update.  It would be nice
if the my file was a little more customizable…although you
already said that was something only the registrar could change 



9-14-00

 Well the my_file link is pretty simple....it loads the html for it in
the nav frame making it a link or just text depending on if you have MF
authorization (you've logged in) and  that link takes you to person.cgi
which loads up the Java script that makes the my file window.  I kind of
already described the way that the course search loads the different
modules   before.  It starts out with a bunch of ifs that will start the
actual searching with type of search as the perimeter for the
call.  Then it makes all the frames, does the specified search, pulling
the data out of the database with sql, and displays the results.  I
learned a lot more about the code while doing the changes and had a
whole lot more fun doing it.  Something that I thought up that doesn't
really make webdb work better (in fact it would make it more
complex) is making custom colors for the different frames. 
Something else that might be nice is to have a way of adding
cousom  links to the nav window.  Another thing that I could think of
was when the search window is made the size of the frame that lets you
choose the courses, field, time, etc...should be at least big enough to
include the get button so you don't have to scroll down to click
it.  The final thing I could think of is that in addition to the
registration card is a window or something that has a visual
representation of what your schedule is (like the M,T,W,R,F schedule
for your current classes)...It could have red blocks or something where
there is a conflict of hours.