] RAD Edit and List Panels
Jonathan Carlson wrote:
>Eelco,
>
>Your approach to the BeanPanel is pretty similar to mine, but instead
>of using BeanInfo objects, I allow the developer to specify the
>attributes and give them a little more control over how the HTML looks
>(size
Jonathan Carlson wrote:
Eelco,
Your approach to the BeanPanel is pretty similar to mine, but instead
of using BeanInfo objects, I allow the developer to specify the
attributes and give them a little more control over how the HTML looks
(size of the text field, text area, etc). Will it be poss
Darn, I always have an "aha" moment right after I hit "send". I see
your FieldPanel for selecting which attributes to edit. It looks like
its going in the right direction. Would it be flexible enough to
support specifying a DropDownChoice for a certain attribute, or the
maximum length of a Text
Eelco,
Your approach to the BeanPanel is pretty similar to mine, but instead
of using BeanInfo objects, I allow the developer to specify the
attributes and give them a little more control over how the HTML looks
(size of the text field, text area, etc). Will it be possible to
specify attributes
Yep, though the fieldpanel gives you more control. I tried to stay close
to a javabean-like pattern (xxxEditor naming schema), though that has to
tighten a bit yet. I also would like to make it less flexible; currently
you can feed it pull models, which is not such a good idea with so much
goin
Thanks Eelco, I'll check it out. It looks like it uses reflection and
lots of default values to allow editing for every single attribute in a
bean. Is that right?
How's JavaOne?
- Jonathan
>>> [EMAIL PROTECTED] 2005-06-30 4:05:54 AM >>>
Did you take a look at the code I put in wicket-example's
Did you take a look at the code I put in wicket-example's HEAD, the
wizard example? There is some bean editing stuff in there that does
things on a whole different way than you propose. Maybe it is a good
idea to check this out, and see what you do and don't like, and have a
discussion on that.