implemented conference hotlists and SIG list management from the Top page;

cleaned up remaining SQL statements using text columns instead of column
indexes with the ResultSet; fleshed out specifics in the TODO for
SIG administration
This commit is contained in:
Eric J. Bowersox
2001-02-19 02:56:16 +00:00
parent 7b7e6be996
commit e23de5dae6
32 changed files with 1400 additions and 111 deletions

24
TODO
View File

@@ -1,8 +1,11 @@
Lots!
- A bunch of the SIG-level functionality is not fully implemented. We need
invites, some admin functions, and the "Manage" button on the "top
content" window to work.
- Unimplemented functions on the SIG Administration page:
Set SIG Features (sigadmin, command=F)
Membership Control (sigadmin, command=M)
Delete SIG (sigadmin, command=DEL)
- Implement SIG invitations ("Invite" button on the profile).
- Should we provide the sysadmin the ability to disable SIG creation for
non-admin users? Maybe there needs to be a "global" set of levels that
@@ -13,8 +16,6 @@ Lots!
before we go live. (It plugs into the Administrative SIG features.)
- Unimplemented functions on the Top page:
Manage SIG list (SIG sidebox)
Manage Conference Hotlist (Conference sidebox)
Customize Sideboxes
- The plan for the "main" part of the Top page is to let a sysadmin put
@@ -25,21 +26,8 @@ Lots!
- Implement quick e-mail from the user profile display (engine support and
UI).
- More SELECT queries that specify discrete columns need to start using
numeric indexes to retrieve the column data, instead of names. This will
make the retrieval process more efficient, and make for shorter SQL
statements in the case of joined queries (no need to SELECT table.column
AS name).
- Slippage during posting is still untested.
- We need a "manage" button at conference list level so we can use that to
manage the ordering of conferences. This operation should be accessible
only to users with "create" privilege on the SIG.
- Conference hotlist is now partially implemented, but we need some more work
at engine level.
- Not everybody likes purple. Provide a way to change the default colors.
Probably via entries in render-config.xml. Of course, if we go to a
different rendering system eventually, we won't need this.