My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
Evolutions_Feature_Plan  
This page just sum up what may appear one day in DocDoku or in Docdoku-widgets.
Updated Aug 28, 2009 by nhanm...@gmail.com

DocDoku feature plan

Core API feature plan

Search

Perform search via query objects, and criteras. The seach result will be encapsulated in an object which will hold several information about the search performed

Pagination

Limit the amount of results in a search. This is partially done in the GWT server side but as it performs a complete search then extract the required chunk, it might be a loss of time in a multi-user/large amount of data context. The purpose is to enhance performance, and simplify code.

Roles

In workflow model edition, a task will not be associated directly to a specific user, but to a role instead. This will allow a fine tuned mapping at workflow instanciation. We can imagine that a role can be mapped by a single user, or a group of users.

Web UI feature plan

Tasks to do

Providing a widget to remind the user the taks he must/can do.

Docdoku-widgets feature plan

SpinBox

Adopt GWT API style

Change the actual Listener system by the Handler mechanism used in recent versions of GWT (using HasHandlers and GWTEvent<I> )

Input

Adopt GWT API style

Change the actual Listener system by the Handler mechanism used in recent versions of GWT (using HasHandlers and GWTEvent<I> )

ButtonMenu

Adopt GWT API style

Change the actual Listener system by the Handler mechanism used in recent versions of GWT (using HasHandlers and GWTEvent<I> )

TableWidget

Selection

Add a better way to manage selections (like SelectionModel in Swing)


Sign in to add a comment
Powered by Google Project Hosting