Ernst Bunders wrote: > there is allso a middle way. We could define a gui defenition language > compareable to the searchquery syntax, where you can define > characteristics of a gui interface element: > <guitype> > <line length="40"> > </guitype>
I think the lenght of value is suficciently defined by its length. The gui can decide on a different presentation length, but I think that is solely a CSS issue. > <guitype> > <textarea width="40" height="10%"> > </guitype> Number of lines is quite hard to fixate, but a reasonable guess would be the length divided by a line-length.. 10% of what? So, you may have a point here, but I don't really get it. If these things still server as a mere indication, that I'd say that the 'actual' maximal length is a good indication too.. > getting all carried away, i think we could even add some kind of > databinding where, for instance in an i18n fieldtype (an xml field with > elements for some content for different languages) you could define a > combination of a dropdown with all supported languages with a textarea > allowing you to edit the contents of the matching element. These things are of course feasible. In the 'guihandler' you'll sometimes need datatype specific information. Perhaps it's even better to match on class of the datatype rather than on identifier, because then you could easilily plug in 'I18NXmlHandler' into taglib. (It's not the name which is important but the class). But actually I think it is possible already. If you define 'i18xml' in datatypexml, then you can associate a typehandler in taglib in 'fieldtypes.xml' of taglib with that string. Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
