...

• don't use JS wrapping classes for widgets: they introduce yet-another-API which is sometimes confusing.
• update the widgets' java public API so that it's more "Rhino-friendly" (check JavaBean conformance and add accessors where needed)

• Wiki Markup
  \[DONE\] implement an equivalent to the bookmark feature of V2, by a function property of the form that gets called at each request roundtrip

• add helper methods to the Form class to create event listeners from JS functions
• restrict the "cocoon" object that's available in the event handlers so that it does not provide response-related methods (sendPage etc)

• Wiki Markup
  \[DONE\] implement widget.getDefinition() (give access to form definition)

• rename showForm() 'bizData' parameter to 'viewData' (a la v3): http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111951875814550&w=2
  

Java code

• Wiki Markup
  \[DONE\] ignore the "action-command" attribute which is currently useless except for repeater-actions and row-actions

• Wiki Markup
  \[DONE\] implement widget states

• Wiki Markup
  \[DONE\] review widget states (maybe an output state is necessary) \\

Binding

• Review repeater binding (http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=109950611823830&w=2)
  

...