Surely sendmail reeled when thusly spake Geert Bevin:
>
> >You talk about using autodiscovery to detect forms variables
> >and forms processing methods, and I think that would be great.
> >I wonder if (for example) it would be useful if an Element
> >could use annotations to declare the forms variables it needs
> >and their default widget types, and with the possibility to
> >declare custom "widget loaders".
>
> Could you expand on this?
I was afraid you'd ask that :-)
Reading (and implementing half of) the JCR (JCP-170, Java Content
Repository) really got me thinking about the representation of
data (and metadata).
If every class variable in my class is a String -- or representable
as one -- then it's just a big damned hash table, and a form builder
can just pluck out values -- legal field values, and maybe also the
text field (e.g. "Customer number:") that is displayed to the user.
Instead of
protected String validSchemas[] { "DocBook", "DITA", "XHTML" };
public void setSchema(String s) { .. ]
public String getSchema() { .. }
I'd like to say something like
@property("readwrite")
@enumerated("DocBook","DITA","XHTML")
@widget("combobox","editable=false") // true iff can define a new value
String schema;
Does this make any sense ? I'm sure I'm overlookin a zilliion
issues here. But if the class declared the form fields it needs,
and then the class was bound to an HTML form, the forms engine
might be able to crank out a lot of boilerplate.
HTH
fred
--
F.Baube * "Happy songs never made me happy.
Georgetown/MSFS/1988 * A lot of sad songs have."
email fbaube#welho.com * -- Mira Aroyo, Ladytron
gsm +358 41 536 8192 *
wmd 60°11'10.8"N 24°57'36.9"E
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
