To do

This page details the outstanding tasks and features to be implemented before a new release version can be created. Please see the task list for minor tasks for the code itself.

Tasks are divided into various categories denoting their importance: 'Feature', 'major', 'medium' and '>minor' in order of importance.

0.1

  • Feature: User framework (logging in/out, registering new users, modifying details).
  • Feature: Project framework (register new projects, add users to admin/editor list, modify project details).
  • Feature: Administration framework - flexible, free-form administration framework that makes it easy to add new administration functionality (user admin, project admin, admin admin).
  • Feature: Document framework - basic document framework (forwaqrd ilnks to documents, display history, etc).
  • Feature: Messaging framework (send messages, add subscriptions, edit subscriptions, admin subscriptions).
  • Feature: Forum framework (create forums, add messages, issue tracking).
  • Major: Fix bug 1040589: we need to be able to add users and set their password settings in Slide WebDAV repository.
  • Major:Create JUnit tests for all classes to give full test coverage. Add cactus testing for Struts actions.
  • Major: Seperate struts application framework into segments (/users/* maps to user operations, /projects/* maps to project operations. Add wildcard actions as well so that projects can be more clearly specified (i.e. /users/ricardo/view.do gives the view screen for the user 'ricardo').
  • Medium: Fix styles so they are smaller, simpler and more legiable. Modify CSS so that it contains more standardised classes.
  • Medium: Add full and detailed Javadoc to all classes.
  • Medium: Implement Maven deploy goal that automatically writes hibernate generated SQL to database. Similarly, maven undeploy and redeploy goals should be implemented.
  • Medium: Eliminate the ViewPage action and use tile definitions directly as forwards.
  • Minor: Do we need the taglibs? Should we just insert the user/configuration directly into the contexts? Perhaps we could create a pico taglib for accessing components in the pico containers?

1.0