You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Antony Stubbs <an...@gmail.com> on 2007/08/30 02:31:52 UTC
Wicket capability for LARGE forms
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...
What are people's experiences? How do you find Wicket to use in very large
forms? Thoughts? Ideas? Alternatives?
(disclaimer - I've only written one page in Wicket, and that was just
playing around with Ajax (NIIIICE!! :)))
http://www.nabble.com/file/p12398507/bigForm.png
--
View this message in context: http://www.nabble.com/Wicket-capability-for-LARGE-forms-tf4351285.html#a12398507
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket capability for LARGE forms
Posted by Maurice Marrink <ma...@gmail.com>.
In our application where we have a similar page, we decided not to use
forms / textfields but instead use editable labels and update with
ajax. it was a real performance gain both in page size as browser
render time.
Maurice
On 8/30/07, Igor Vaynberg <ig...@gmail.com> wrote:
> yeah, with ajax instead of simply disabling them you can remove them
> completely, or replace them with something else entirely.
>
> however, if all you really want to do is to make them disabled on clientside
> that should work also. might not be as straight forward but should work.
>
> -igor
>
>
> On 8/29/07, Antony Stubbs <an...@gmail.com> wrote:
> >
> >
> > 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 <an...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> > >
> >
> > --
> > 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket capability for LARGE forms
Posted by Igor Vaynberg <ig...@gmail.com>.
yeah, with ajax instead of simply disabling them you can remove them
completely, or replace them with something else entirely.
however, if all you really want to do is to make them disabled on clientside
that should work also. might not be as straight forward but should work.
-igor
On 8/29/07, Antony Stubbs <an...@gmail.com> wrote:
>
>
> 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 <an...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
>
> --
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicket capability for LARGE forms
Posted by Antony Stubbs <an...@gmail.com>.
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 <an...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket capability for LARGE forms
Posted by Eelco Hillenius <ee...@gmail.com>.
On 8/29/07, Antony Stubbs <an...@gmail.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket capability for LARGE forms
Posted by Martijn Dashorst <ma...@gmail.com>.
You are aware of what you are doing to your browser? There is a limit
to the pain you can cause. I'm calling the People for the Ethical
Treatment of Web Browsers!
Seriously: there is a limit to the number of form controls you can put
in a page (around ~1000 iirc)
Martijn
On 8/30/07, Antony Stubbs <an...@gmail.com> 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...
>
>
> What are people's experiences? How do you find Wicket to use in very large
> forms? Thoughts? Ideas? Alternatives?
>
> (disclaimer - I've only written one page in Wicket, and that was just
> playing around with Ajax (NIIIICE!! :)))
>
> http://www.nabble.com/file/p12398507/bigForm.png
> --
> View this message in context: http://www.nabble.com/Wicket-capability-for-LARGE-forms-tf4351285.html#a12398507
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org