the table, we call a method in the table helper class. That method returns 3
things.. an array of SELECT columns, an array of FROM tables, and an array of
WHERE clauses. The table editor takes these, adds ORDER, LIMIT, etc, and
runs the sql.
- Update the table editor to allow variables to be set. THe helper class reads
these variables to do pretty much anything it wants.. In this commit, it
reads the judges_show_what variable, to determine how to format the SQL for
selecting the table of judges (so the calling php can now know NOTHIGN about
the database, it just sets a variable and expects the data to be formatted
correctly.
- Update the judge manager, show all judges should now SHOW ALL JUDGES.
have admin access to access the committee editor)
- Put a "My Profile" link on the main nav bar once a committee member logs in,
so they don't have to find themselves thorugh the committee editor. It takes
them right to editing their own profile.
- Admin can use the tour manager to add tours
- Admin can use the config variables to enable tours, and select the min/max number of tour choices.
- Students will see a "Tour Selection" section of registration, which is incomplete until the student has selected at least a minimum number of tours.... actually, this may be broken.. Need to look at it further..
Add ability to create access codes for all schools and to remove access codes from all schools
Update generatePassword to accept a password length as a parameter, defaults to 8
Add two new projectnumber options: c=category shortform, d=division shortform, eg (JLS01 = Junior, Life Science, Project #01)
Add shortform field for age category
Fix bug in config editor where it was updating values for ALL years, instead of just the current year!
Bump version number to development version
table
- Add complete and year options to the judge manager, filter by ALL, active and
inactive for the current year, or active only.
- Add the "complete" status the the judge info page (the judge info popup page
needs to be integrated with the new judge manager, somehow.. so we can remove
the judges_judges list page).
- Put a total at the top of the judge manager list
- Add to the table editor:
- Change the filter to accept a single argument, so we're not
restricted to the `$k`='$v' syntax, we want to be able to filter on a
table JOIN.
- Add a additionalListTable variable, and additionalListTable()
function, to specify additional tables that should be part of the
table select statement. I guess ideally the class would implmenent
their own if alternative behaviour was desired. But this way is
pretty generic. The table editor can now, for example, select judges
by year.
should be SELECTED in the select type. If the keys are 0, and there is no
data, PHP does a numeric compare and matches them, when they shouldn't
actually be matched.
- Add Load/Save for the judge category preferences
- Enable saving to mysql. It works.
- Update the tableeditor css to use the same colours as sfiab
that allows you to customize the size of the labels to suit _ANY_ label
stock paper.
Add to label generator the option to get judge mailing labels, and award
sponsor mailing labels, and make it easy to add more mailing labels
down the road (students? committee? etc?)
Add two default label stocks (Avery 1"x4" and Avery 2"x4")
- Added a "multicheck" input type for languages (english, french)
- Added a proof of concept cross reference to the judge class, it pulls the
languages out of the judges_language database
- Completely broke the save mechanism.
- Converted the tableeditor edit routines to read from the input class
- Converted the tableeditor edit routines to use assoc arrays, instead of ->
(easier to pull from mysql and then add cross references to it.
- Add the table editor style sheet, and load it in the header (needs editing)
- Add a judge class (not complete)
- Add a judge manager php file that doesn't interfere with what's already in the system
THis is a proof of concept, it sorta works, but the table editor is still reading directly from the judges class. It will be updated to make calls only into the calling class type, thus abstracting away all the SQL stuff, and allowing the group class (judge in this case) to hide
all the cross table references we need to make for loading, saving, deleting, etc.
