intentions
Time I started laying out the intentions for implementation of AgileWiki3.
- A bit of cleanup on the top-level framework. Sessions in particular should have some kind of timeout mechanism. Otherwise we've got a memory leak, as restarting the client simply opens a new session.
- The AwServer and clients should continue to work "out of the box", but we also need to be able to configure the RMI. A different port may be needed. And when running the client on a different machine, you need to specify the host. I'm thinking an optional property file might be good here.
- We need a servlet to drive the web interface. (No, not SOAP. Not for a while!) I'm thinking this should be a priority, least we design ourselves into a corner with Swing, otherwise I'd put it off.
- CEnts are being displayed, but how about LEnts and DEnts? Need to verify this or fix it.
- We need to be able to change all the necessary CEnts/LEnts/Dents. Some are done. Easy stuff, with a slight complication for access control. We also need to be able to edit documents and tables, as well as create Rolons.
- Privacy needs to be implemented early, restricting the ability to view content. Two use cases here: (1) restricting visibility of a cabinet to a user group and (2) restricting visibility of personal content to the user, e.g. user email address. We don't do it early and it gets very diffilcult.
- Support for navigation by pathname.
- We need to support WikiWords in documents, and citations.
- Real live classifiers: include, export, tagmatch, importmatch, importtag, export.
- rename/refactor
- move/refactor
- restore
- post
- destroy
- promote/demote
- dump/snap/restore
- calendar
- A guestUI.
- A rolonicUI.
- Row entry form for tables.
- Table descriptor creation wizard.
- Deligation of privileges.
- sharing between arks
- cabinet proxies
Bill
0 Comments:
Post a Comment
<< Home