55 lines
2.1 KiB
Plaintext
55 lines
2.1 KiB
Plaintext
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.
|
|
|
|
- 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
|
|
aren't hardcoded. Where do they get stored? The database? (Maybe the
|
|
nice shiny new "globals" table?)
|
|
|
|
- There's no system admin functionality AT ALL. We need to have this stuff
|
|
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
|
|
notices there by "publishing" selected conference messages to the front page.
|
|
We may include a welcome message up top to be displayed if the user's not
|
|
logged in.
|
|
|
|
- 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.
|
|
|
|
- Javadocs. Lots of javadocs.
|
|
|
|
- I haven't explored the possibility of using Tomcat-Apache integration yet.
|
|
This is something I'd like to explore one day. We may need it for EMinds.
|
|
Actually, we probably will.
|
|
|
|
- Continue pressing on. "Failure is not an option."
|
|
|