Emile wrote: > > This may partially be addressed by the field-types project; it is about > > configuring more meta-data about fields and providing access and use of > > that. That would. e.g. elimate the need for specifying those kind of > > things again in your editor-implementation (like occurs now in > > editwizard). > > > > Michiel > > Hi Michiel > > I think the need extends further than field level - even for validation, one > sometimes has groups (as in the case of radio buttons) or dependent > fields.
Yes, of course. I also said 'partially'. We will focus on constraints on a single fields first, but interdependency of fields can of course also be addressed in this project. It will be simple to implement a check for the validity of a certain field, even if that is dependent on other fields. I have no real clue how to communicate in some comprehensible way this kind of information to the client, for javascript impelmentaiton of the same or so. > Beyond that, there are often complexities in relationship structure, complex > objects - whereby the data type is not known unless it's parent and > grandparent classes or types are known, dependent relationships, dynamic > objects which are defined by the relationships they keep - one of numerous > possibles (such as a field item, which may be a data entity, or a group of > data entities, which has a recursive link back into the data entity object). > These are all examples I've used, there must be plenty more. These were > obviously achieved with custom pages and plenty of associated logic. I figure that much of this stuff will for some time remain to be customized on the JSP's/javascript. Or would you have hope to define these kind of things genericly? Perhaps it is easiest to talk back to the server with request for validity only, which it then can report, without crashing an exception to the poor user. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
