Ah yes, DataTable, I see, like a data grid... And what about changing the fields to enabled / disabled? Staying within Wicket I suppose the nicest way would be ajax onChange behaviour on the initial drop down box?
Eelco Hillenius wrote: > > On 8/29/07, Antony Stubbs <[EMAIL PROTECTED]> wrote: >> >> I have a couple of pages with _very large forms_, that are also modified >> dynamically to set which fields are editable using javascript, dependant >> on >> the value of a drop down list. Please see the example image attached. And >> that's only the first page.... >> the application is in - *gasp* - struts. >> I love what I've seen so far with Wicket, but I'm unsure what it's like >> to >> use compared to say, Stripes, Struts 2, Click, Tapestry etc when it comes >> to >> very large forms. >> being that setting up each field in wicket is kinda verbose... > > Yeah, you definitively should not just add all these examples by hand :) > > What you do is e.g. use a DataTable component. The data provider would > return the rows, and you define the columns on that data table. Rest > should be straightforward. Don't forget to set the itemReuseStrategy > if you're working inside a form (e.g. to use ReuseIfModelsEqual). > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Wicket-capability-for-LARGE-forms-tf4351285.html#a12399482 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
