[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-cocoon-docs
Subject:    [DAISY] Updated: Simple XML Binding
From:       daisy () cocoon ! zones ! apache ! org
Date:       2006-11-17 12:01:39
Message-ID: 25093773.1163764899918.JavaMail.daisy () cocoon ! zones ! apache ! org
[Download RAW message or body]

A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/743.html

Document ID: 743
Branch: main
Language: default
Name: Simple XML Binding (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 11/17/06 12:01:31 PM
Updated by: Helma van der Linden

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 1655 bytes (previous version: 1656 bytes)
Content diff:
(3 equal lines skipped)
    <h1>Concept</h1>
    
    <p>As an alternative for the more flexible <a href="daisy:488">binding
--- framework</a>, there is also a simpler solution when that can be used when there
--- is a 1-to-1 coupling between the XML and the form.</p>
+++ framework</a>, there is also a simpler solution that can be used when there is a
+++ 1-to-1 coupling between the XML and the form.</p>
    
    <p>The XML format is such that there is one XML element for each widget and the
--- element gets the widget id as name. Exceptions from this is that the elements in
--- a <a href="daisy:496">repeater</a> get the name "item" and an attribute
+++ element gets the widget id as name. Exceptions from this are that the elements
+++ in a <a href="daisy:496">repeater</a> get the name "item" and an attribute
    "position" with the position of the repeater child, instead of just a number
    (which is not allowed as element name). Childs of a
--- <a href="daisy:490">MultiValueField</a> are also embeded within an "item"
--- element. If the Form widget does not have an id it get the name "unknown".</p>
+++ <a href="daisy:490">MultiValueField</a> are also embedded within an "item"
+++ element. If the Form widget does not have an id it gets the name "unknown".</p>
    
    <p>An AggregateField can both be interpreted as one value and as several
--- widgets. This ambiguity is resolved by chosing to emit the single value rather
+++ widgets. This ambiguity is resolved by choosing to emit the single value rather
    than the fields as XML. For population of the form both forms are however
    allowed.</p>
    
(18 equal lines skipped)

[prev in list] [next in list] [prev in thread] [next in thread]