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

List:       binarycloud-dev
Subject:    [binarycloud-dev] node ehancement before rc1
From:       Jean-Christophe Michel <jc.michel () symetrie ! com>
Date:       2004-03-22 11:31:41
Message-ID: 1079955101.702.3159.camel () pwbjcm ! symetrie ! net
[Download RAW message or body]

Hi all,

We spoke with alex on irc (binarycloud/docs/irc/2004-03-20.log)
and i think we got the solution with more control on children and not
more complexity.

Here are the main points:
- in ndf, <children> is replaced by <contains>
(-> changes in dtd and xsl, and in existing ndfs)
This makes clear that definitions don't automatically become children
objects.

- add a property 'definition' that holds the definition of the node

- in Node, we add a AddChildFromContains($id) method
that will load the definition from $this->definition['contains'][$id]
instanciate the object and return a ref on it (probably using existing
AddChild)

- in Node, rename Main() to Render() everywhere

- write a default Node::Init() that calls AddChildFromContains() to act 
as a container if no logic is added into and extended Init().

- alex & jason will provide real cases problems that we should address with node,
table and form, and we'll try to provide the 'best coding' to solve them.

- we need to explore the form: namespace syntax alex provided on irc to replace
the form:elemrole

- we need to test and see if it's possible to remove owner/owned_list from Node
to keep it simpler. Only currently used in Form to SetValues to FormInputs through
the FormComponents.

Feel free to enter more issues and start them.

-- 
Jean-Christophe Michel <jc.michel@symetrie.com>
Symétrie


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@binarycloud.tigris.org
For additional commands, e-mail: dev-help@binarycloud.tigris.org


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