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.
only remove the judge from the current year. The editor needs a field to say
if the judge is registered for the current year or not.
- Delete also needs to somehow express that the judge will be deleted for the
current year only. Which means we should probably implement a Purge, to
completely wipe a judge out of the system.
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")
- Moved the tableeditor class to accept a generic class, no longer a person
class
- Restored the original functionality where everything is specified in the
constructor, but added a 'class' which can be a dummy class to return to the
original tableeditor functionality. The tableeditor checks for
class->tableEditorLoad() now, and if that exists it calls it. If it doesn't
then it calls a default Load() routine which contains the original code from
the tableeditor. Same with save.
Still needs work, but it's getting there.
- Remove the mysql query on EditSave and NewSave
- Unify the EditSave and NewSave code. Now that this is done, I will move the
SQL generation task to the group class, so all the editor has to do is
instantiate a person class, set some values, and call the save() function.
- 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.
Also do now display any sort of login (email) box if we're before registration open, but do
show it if we're after registration close so they can still login and view info or apply for
special awards
- Dates are always displayed in the same order, which is somewhat logical.
- It detects some errors. It's not perfect, but it'll detect when a date is
invalid, and when pairs of dates are bad (eg. the reg. system closes before
it opens.). All dates are still saved to the database but the user is
alerted of any date errors.
