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: TimLarson
Date Sat, 03 Jul 2004 12:25:33 GMT
   Date: 2004-07-03T05:25:32
   Editor: JoergHeinicke <joerg.heinicke@gmx.de>
   Wiki: Cocoon Wiki
   Page: TimLarson
   URL: http://wiki.apache.org/cocoon/TimLarson

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -5,12 +5,12 @@
 
 ----
 
-=== Current Project(s) ===
+= Current Project(s) =
 
  * Form and report design GUI
-  *Initially for Woody (Woody) and [http://xreporter.cocoondev.org xReporter], but hopefully
others will find additional uses.
+  * Initially for ["Woody"] and [http://xreporter.cocoondev.org xReporter], but hopefully
others will find additional uses.
   * Involved creating the !EffectTransformer. This allows the structure of the source code
of Java XML transformers to match the structure of the data being transformed.
-  *Required adding support to Cocoon Forms for dynamic creation and deletion of widgets approximately
as described in this [http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106330721523801&w=2
email]. See below for the results thus far.
+  * Required adding support to Cocoon Forms for dynamic creation and deletion of widgets
approximately as described in this [http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106330721523801&w=2
email]. See below for the results thus far.
 
 Additional topics/links:
 
@@ -39,30 +39,18 @@
 [http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107394380308564&w=2 Email Link]
(skip down to the part that starts: "Allow model, binding, and template fragments to be associated
with each other")
 
 ----
-----
-
-=== ==== Update ==== ===
-
-The features described below are present in Cocoon version 2.1.4, but
-they are being redesigned at WoodyScratchpad.  Please join the discussion
-to make sure these features get properly designed meet your needs.
-
-----
-----
 
 = New features for Cocoon Forms (Woody): =
-= Class, New, Struct, and Union =
 
-== Preface ==
+== Update ==
 
-All aspects of this implementation are open for discussion and change.
-While the features are definitely needed, the way it is coded, the names that
-were chosen, etc. can all be changed as we decide as a community.
-Please consider this as seed code that we can all grow in the way we see fit.
+The features described below are present in Cocoon version 2.1.4, but
+they are being redesigned at ["WoodyScratchpad"].  Please join the discussion
+to make sure these features get properly designed meet your needs.
 
-A primitive sample form creation/editing GUI is also provided in the patch.
+== Class, New, Struct, and Union ==
 
-== Quick summary ==
+=== Quick summary ===
 
 Combined use of these new features allow for the creation of dynamic, recursive
 GUI's and editors for structured content of any nesting level.  See "TODO" below
@@ -70,17 +58,17 @@
 to use Cocoon Forms to create and edit sitemaps, form definitions and templates,
 xreporter reports, etc.
 
-=== Class ===
+==== Class ====
  * Definition element used to create a reusable collection of widget definitions.[[BR]]
  * Template element used to create a reusable collection of templates and/or markup.
 
-=== New ===
+==== New ====
  * Definition element used to insert the widgets from a referenced class.[[BR]]
  * Template element used to insert the templates and/or markup from a referenced class.
 
 TODO: Should describe plans for class instantiation parameters, etc. here.
 
-=== Struct ===
+==== Struct ====
 Container widget which can hold zero or more widgets.[[BR]]
 This wraps the set of contained widgets in their own namespace (the id of the Struct widget),
 allowing the same widget id's to be reused multiple times in a form.  Also, using a Struct
@@ -88,7 +76,7 @@
 
 TODO: Should describe the use of the corresponding template element here.
 
-=== Union ===
+==== Union ====
 Discriminated union widget which holds one of several possible widgets at any one time.
 
 TODO: Should describe the use of the corresponding template elements here.
@@ -103,9 +91,9 @@
 derived widgets which reference other derived widgets (order of evaluation issues).
 [This change has now happened, and is reflected in the detailed notes below.]
 
-== Detailed descriptions: ==
+=== Detailed descriptions: ===
 
-== Class ==
+==== Class ====
 Specify a set of widget definitions or templates and/or markup for reuse.
 The same concept is implemented in the form definition for
 widget reuse, and in the form template for template and/or markup reuse.
@@ -113,69 +101,69 @@
 '''Definition syntax'''[[BR]]
 Only allowed as a direct child widget of wd:form.
 Note that the definition class id's currently form a flat namespace.
-{{{
-<wd:class id="some-class">
-  <wd:widgets>
-    <!-- A list of any widgets(s) (e.g. wd:field, wd:new, wd:struct, wd:union) -->
-    [...]
-  </wd:widgets>
-</wd:class>
+{{{
+<wd:class id="some-class">
+  <wd:widgets>
+    <!-- A list of any widgets(s) (e.g. wd:field, wd:new, wd:struct, wd:union) -->
+    [...]
+  </wd:widgets>
+</wd:class>
 }}}
 '''Template syntax'''[[BR]]
 Inside the wd:form template, allowed anywhere other templates are allowed
 Note that the template class id's currently form a flat namespace
-{{{
-<wt:class id="some-class">
-  <!--
-    A list of templates and/or markup
-  -->
-</wt:class>
+{{{
+<wt:class id="some-class">
+  <!--
+    A list of templates and/or markup
+  -->
+</wt:class>
 }}}
 
-== New ==
+==== New ====
 Insert the widgets or templates and/or markup from the referenced class.
 
 '''Definition syntax'''[[BR]]
 New inserts the widgets from the referenced class.
-{{{
-<wd:new id="some-class"/>
+{{{
+<wd:new id="some-class"/>
 }}}
 '''Template syntax'''[[BR]]
 New inserts the templates and markup from the referenced class.
-{{{
-<wt:new id="some-class"/>
+{{{
+<wt:new id="some-class"/>
 }}}
 
-== Struct ==
+==== Struct ====
 Generic container for widgets.
 Useful to hold multiple widgets in a union case, and anywhere
 there is a need to wrap a collection of widgets in a namespace.
 
 '''Definition syntax'''
-{{{
-<wd:struct id="some-struct">
-  <wd:label>...</wd:label>
-  <wd:hint>...</wd:hint>
-  <wd:help>...</wd:help>
-  <wd:widgets>
-    <!--
-      A list of any widget(s) (e.g. wd:field, wd:new, wd:struct, wd:union)
-    -->
-    [...]
-  </wd:widgets>
-</wd:struct>
+{{{
+<wd:struct id="some-struct">
+  <wd:label>...</wd:label>
+  <wd:hint>...</wd:hint>
+  <wd:help>...</wd:help>
+  <wd:widgets>
+    <!--
+      A list of any widget(s) (e.g. wd:field, wd:new, wd:struct, wd:union)
+    -->
+    [...]
+  </wd:widgets>
+</wd:struct>
 }}}
 '''Template syntax'''
-{{{
-<wt:struct id="some-struct">
-  <!--
-    A list of templates for contained widgets, possibly mixed with markup
-  -->
-</wt:struct>
+{{{
+<wt:struct id="some-struct">
+  <!--
+    A list of templates for contained widgets, possibly mixed with markup
+  -->
+</wt:struct>
 }}}
 
-== Union ==
-Discriminated union.  Each direct child widget is considered a union case.
+==== Union ====
+Discriminated union. Each direct child widget is considered a union case.
 The widgets are only created when their case is selected (lazy construction),
 but their values continue to exist after switching to another case, to allow
 for case-switching validation, value copying between cases, and automatic
@@ -186,77 +174,77 @@
 current case.
 
 '''Definition syntax'''
-{{{
-<wd:union id="widget-id" case="widget-id">
-  <wd:label>...</wd:label>
-  <wd:hint>...</wd:hint>
-  <wd:help>...</wd:help>
-  <wd:datatype base="...">
-    [...]
-  </wd:datatype>
-  <wd:selection-list .../>
-  <wd:on-value-changed>
-    ...
-  </wd:on-value-changed>
-  <wd:widgets>
-    <!--
-      A list of any widget(s) (e.g. wd:field, wd:new, wd:struct, wd:union)
-    -->
-    [...]
-  </wd:widgets>
-</wd:union>
+{{{
+<wd:union id="widget-id" case="widget-id">
+  <wd:label>...</wd:label>
+  <wd:hint>...</wd:hint>
+  <wd:help>...</wd:help>
+  <wd:datatype base="...">
+    [...]
+  </wd:datatype>
+  <wd:selection-list .../>
+  <wd:on-value-changed>
+    ...
+  </wd:on-value-changed>
+  <wd:widgets>
+    <!--
+      A list of any widget(s) (e.g. wd:field, wd:new, wd:struct, wd:union)
+    -->
+    [...]
+  </wd:widgets>
+</wd:union>
 }}}
 '''Template syntax'''[[BR]]
 The wt:union template outputs any markup outside of the cases and the contents of the
 wt:case template for the current union case, while suppressing output from the other
 wt:case templates.
-{{{
-<wt:union>
-
-  <!-- A list of union cases, possibly mixed with markup. -->
-
-  <!-- Use an empty id to handle the case of an empty union discriminant. -->
-  <wt:case id="">
-    <!-- Any markup -->
-  </wt:case>
-
-  <!-- Use the union child widget id as the case id. -->
-  <wt:case id="some-case">
-    <!--
-      A list of any relevant templates, possibly mixed with markup.
-    -->
-  </wt:case>
-
-</wt:union>
+{{{
+<wt:union>
+
+  <!-- A list of union cases, possibly mixed with markup. -->
+
+  <!-- Use an empty id to handle the case of an empty union discriminant. -->
+  <wt:case id="">
+    <!-- Any markup -->
+  </wt:case>
+
+  <!-- Use the union child widget id as the case id. -->
+  <wt:case id="some-case">
+    <!--
+      A list of any relevant templates, possibly mixed with markup.
+    -->
+  </wt:case>
+
+</wt:union>
 }}}
 '''Binding syntax'''[[BR]]
 The wb:union binding wraps wb:case bindings.  The wb:case binding that matches the
 current case of the surrounding union is the only wb:case binding which will perform
 its child bindings.
-{{{
-<wb:union>
-
-  <wb:case id="">
-    <!-- A list of bindings relevant to the default case -->
-  </wb:case>
-
-  <wb:case id="some-case">
-    <!-- A list of bindings relevant to the selected case -->
-  </wb:case>
-
-</wb:union>
+{{{
+<wb:union>
+
+  <wb:case id="">
+    <!-- A list of bindings relevant to the default case -->
+  </wb:case>
+
+  <wb:case id="some-case">
+    <!-- A list of bindings relevant to the selected case -->
+  </wb:case>
+
+</wb:union>
 }}}
 
 === TODO: ===
  * Fix issues with nested Repeater's:
-  *Forgetting values on Union case switch. (broken in 2.1.5, fixed in CVS)
+  * Forgetting values on Union case switch. (broken in 2.1.5, fixed in CVS)
  * Finish "Form GUI" sample:
-  *Correct and finish the save side of the binding to allow saving the edited form.
-  *Add the rest of the widgets and options.
-  *Add display of form as it is created, possibly using frames.
-  *Replace the XSP success page with a JX page.
-  *Create samples for a form template GUI, form binding GUI, etc. and combine them into a
complete form creation and editing GUI.
-  *Get somebody with HTML and CSS knowledge to smooth out the visual design.
+  * Correct and finish the save side of the binding to allow saving the edited form.
+  * Add the rest of the widgets and options.
+  * Add display of form as it is created, possibly using frames.
+  * Replace the XSP success page with a JX page.
+  * Create samples for a form template GUI, form binding GUI, etc. and combine them into
a complete form creation and editing GUI.
+  * Get somebody with HTML and CSS knowledge to smooth out the visual design.
  * Add automatic selection list generation to the union widget definition.
  * Add a test to !NewDefinition.resolve for union defaults that would case a non-terminating
recursion.
  * Make the non-terminating recursion detection more efficient.

Mime
View raw message