> Anyway, I think the main flexibility should cover the looks of the panel > and the ordering of fields. Furthermore, I think the BeanInfo like > pattern I used is usefull for breaking out of the default field > rendering. What do you think?
I think that flexibiliy is good enough. OGNL provides a lot of flexibility with showing info from related instances in lists assuming we can use PropertyModels. I really like your BeanInfo approach. It allows for "no work" panels as well as providing more flexibility about which properties and what order. - Jonathan ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
