I'm giving up on BeanEdit. Anyway, if some have an idea what's wrong, I like to hear it.
Now I'm not even sure that kind of custom rendering of properties is possible at all. On Mon, Jan 26, 2009 at 2:25 PM, Davor Miku <davorm...@gmail.com> wrote: > Yes, I understand that, but with <t:parameter /> I should be able to > override that, and to provide my own rendering > of categories property. At least, that's how I understood documentation. > > > > > On Mon, Jan 26, 2009 at 3:12 PM, Thiago H. de Paula Figueiredo < > thiag...@gmail.com> wrote: > >> Em Mon, 26 Jan 2009 16:01:37 -0300, Davor Miku <davorm...@gmail.com> >> escreveu: >> >> I'm not getting it. >>> >> >> I'm sorry, I could have been clearer. The relevant part of the >> documentation is: >> >> "The default set of property types supported by BeanEditForm: >> * String: as a text field >> * Number: as a text field >> * Enum: as a drop-down list >> * Boolean: as a checkbox >> * Date: as a JavaScript calendar" >> >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java consultant, developer, and instructor >> http://www.arsmachina.com.br/thiago >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> >
