cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: 22StabilizeCocoonForms
Date Tue, 30 Nov 2004 08:31:42 GMT
   Date: 2004-11-30T00:31:41
   Editor: ReinhardPoetz <reinhard@apache.org>
   Wiki: Cocoon Wiki
   Page: 22StabilizeCocoonForms
   URL: http://wiki.apache.org/cocoon/22StabilizeCocoonForms

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,4 +1,26 @@
-Describe 22StabilizeCocoonForms here.
-1.Adding and finish widget state
-2.Unify flowscript v1/v2/v3
-3.Enabled modify form define through api
+= Flowscript integration =
+ * 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)
+ * 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)
+ * implement widget.getDefinition() (give access to form definition)
+
+= Java code =
+ * ignore the "action-command" attribute which is currently useless except for repeater-actions
and row-actions
+ * [DONE] implement widget states
+ * 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)
+
+= Misc =
+ * write a form definition schema so that definitions can be optionally validated.
+ * flatten the CForm-related component in cocoon.xconf. This will ease the transition to
a non-Avalon container 
+ * restructure resources directory (group XSLs and put them into their own directories)
+ * second wizard example - shows how one form that is used in several templates can be controlled
by Flowscript
+ * Review multi-form-per-page - does it work? - provide a sample
+
+= Requests for enhancement (not discussed and/or aggreed yet)
+ * Enabled modify form define through api
+ * Remove everything that has been depracated (union/struct, old validators, ...)

Mime
View raw message