51 lines
2.1 KiB
Plaintext
51 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?
|
||
|
|
|
||
|
|
- 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.)
|
||
|
|
|
||
|
|
- Implement quick e-mail from the user profile display (engine support and
|
||
|
|
UI).
|
||
|
|
|
||
|
|
- The whole "top" display thing needs a serious realignment. The present
|
||
|
|
system is a bit klunky and will be tough to implement Customize. We need
|
||
|
|
the capability to support JSP-based rendering in the individual "top" content
|
||
|
|
panes as well.
|
||
|
|
|
||
|
|
- 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).
|
||
|
|
|
||
|
|
- Getting conferencing in there - but still not there yet. We need topic and
|
||
|
|
post implementations, and UI.
|
||
|
|
|
||
|
|
- Implement conference hotlist for users.
|
||
|
|
|
||
|
|
- The HTML checker is back together and almost all integrated into the
|
||
|
|
Venice engine, but I still need to initialize the dictionary. It's going
|
||
|
|
to require configuration entries in the Venice XML config file, and the
|
||
|
|
use of LazyLexicon (to load the dictionary in the background while people
|
||
|
|
log in).
|
||
|
|
|
||
|
|
- 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."
|
||
|
|
|