Cool! Thanks a lot everybody. No need to reinvent the wheel.
On 11/30/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > > I already did this here: > > http://issues.apache.org/jira/browse/TAPESTRY-628 > > It's pending approval though. Of course, some improvements can be done > (reflection can be very expensive for some needs). > > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > Todd Orr wrote: > > Thanks for your quick reply. You have a point. There is a great deal of > > flexibility in the Tapestry approach. It does seem to sacrifice some > > simplicity, though. I believe in the utility of Tapestry because it > makes my > > development tasks easier, in general. So, I believe it would help to > have a > > framework component as described. I do think that the binding to a value > is > > insufficient for a generalized list approach. I would most appreciate an > API > > that allowed me to bind one property to the option's display and one to > its > > value attributes. I think I could knock this one out. Does anyone have > any > > more input on this? > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
