On Mon, 2006-06-19 at 11:56 +0200, Martijn C. Vos wrote: > Bruno Dumon [mailto:[EMAIL PROTECTED] wrote: > > > > > I think Cocoon only needs one tree model and that is a tree > > > model based on > > > XML. The selection-list widget has the possibility to > > > declare static content > > > in the form definition and can also refer to an xml > > > document in the src > > > attribute. Something like that would be nice for the tree widget. > > > > I don't see why the tree widget should be limited to XML models only, > > the selection list isn't limited to that either (see e.g. the jxpath > > selection list). Dictating to use XML would again require needless > > conversions from Java to XML when it is not needed. > > I don't think it should necessarily be the only one, but it > definitely should be the default tree.
Sure, that would make sense. > Everything can be converted > to XML, and Cocoon is designed around XML. The only reason to use > something else is to skip a conversion step and save a bit of > time, but unlike the current trees, a good XML tree can do anything. > > > mcv. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
