Tony Collen wrote:
Reinhard Poetz wrote:
Thanks Tony for digging into this. It seems to be a very promising way! :-)
(I will comment on the details in a separate mail as soon as I have enough time thinking more about this!)
I know, Dreamweaver is commercial but is there any way putting your work into an opensource CVS/SVN?
There's no functionality yet, it's a completely hollow GUI mockup :) I think the first step might be to create a tag library for the CForms stuff, so I'll start looking into a CForms grammar somewhere.
First an assumption (I'm not sure if this is correct as I haven't had the time yet diving into the load of Dreamweaver documentation):
- Dreamweaver needs a library that contains HTML snippets and those snippets can be used in a WYSIWG mode
As we have a library with all possible form elements (widget definitions) we can create with XSLT that Dreamweaver library:
<fd:field id="xxx"> <fd:label>xxx</fd:label> <fd:datatype base="string"/> </fd:field>
This is transformed into "augmented" HTML:
<!-- <ft:widget id="xxx"> <fi:styling list-type="listbox" listbox-size="2"/> </ft:widget> --> <select name="xxx"> <option name="x" value="bla"/> </select>
Then we have a (cachable) generator that creates the 'correct' CForms template markup.
I think this is the easy part. More difficult is IMHO
- data binding - nested widgets (e.g. repeaters) - make it possible to parameterize the widgets (e.g. the styling)
And I think we need an equivalent to the several container widgets that are available in the different XML application languages (Flex, XUL, XAML). Currently we have tabs but things like output-tables (provides sorting, paginating, ...), hboxes/vboxes, ... are missing.
-- Reinhard
