Alessandro
The information you pointed me too, is certainly of interest to me. I think I'm looking more at automation of the production of simple default XForms. So this relates more to the tree control, as talked about by Pascal and Erik. A tree control can describe the schema, the XML and default functionality of the forms. Because everything is so well structured in XML and XForms, it is easy to go from a high level definition of the form to a working example. This could mean that admin staff could specify structural changes in the form, without needing to go into the detail of XML, via adding, deleting and renaming nodes, and choosing the options for display. So this makes it easier for developers of XForms, or even admin staff who aren't normally developers, to design the form to requirements specified without having to worry about technical issues. This relates to my PhD thesis of enabling non-programmers to create software, as well as my day work. The extra functionality that can't be specified as easily by non-experts in a visual interface can be added afterwards. I think you're so close to solving this issue, as your software is already easy to use for a technical person, systematic, and just needs this top layer user interface for others.
Peter
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
