Johannes Verelst <[EMAIL PROTECTED]> wrote: > Any comments? It's probably a good idea. The only remark that I would like to make is that the possible values of a certain field, are actually not related to editwizards. The field-types project was a.o. started to be able to define such a thing more generally. If e.g. the possible values of one field follow from the result of some query, I'd say that you should define that query inside the definition of the field itself, somehow. That would of course also imply changes to dove and editwizard, because the concept of 'possible values' must be transferable by the dove-protocol.
When this is finished, all optionslist can be removed from editwizards, because everything is automaticly determined by the field's specialization definition. It will then of course also be available to other editors, like taglib-editors or so. So, my hope is that every change on this field might soon become deprecated... We do need a good inventory of what kind of lists of possible values there are, becasue those need be 'definable', preferabbly without to much of java-coding. This will also imply other constraints like minvalue and maxvalue for floats and so on (The possibilities are endless so the trick will be to find something reasonably simpl, yet feasible enough to cover most things one might want). Michiel -- Michiel Meeuwissen Mediacentrum 140 H'sum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
