Many thanks for all the options!
Since I'm on the subject of large forms, I was wondering what you opinion of
appropriate class / db design is for such cases (300+ fields)? I was
thinking of splitting the form into a number of sub-forms each with its own
entity / table. The main issue
Hi,
read here for a start:
http://stackoverflow.com/questions/12120256/generate-html-from-java-beans-at-compile-time
Have fun
Sven
On 23.02.2015 17:10, ChambreNoire wrote:
Hey there,
In the case of large forms with 20+ fields, how should one go about coding
the wicket components? I have
Hey there,
In the case of large forms with 20+ fields, how should one go about coding
the wicket components? I have a large form of over 300 fields divided into
20 pages to code. Instantiating and wiring up each of these one by one would
take an age.
Any ideas?
Many thanks,
CN
--
View
://apache-wicket.1842946.n4.nabble.com/Large-forms-tp4669718p4669720.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
it there's nothing more recent? I'll have to
implement something myself (and these two projects will certainly be useful
for inspiration).
Thanks
CN
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Large-forms-tp4669718p4669720.html
Sent from the Users forum
We have developed something like this at our company, and open sourced it a few
months ago.
Take a look at https://github.com/premium-minds/wicket-crudifier
Sorry, but we have yet to provide proper documentation and examples.
There is, as of today, an example here
23.2.2015 v 17:10 ChambreNoire napsal(a):
Hey there,
In the case of large forms with 20+ fields, how should one go about coding
the wicket components? I have a large form of over 300 fields divided into
20 pages to code. Instantiating and wiring up each of these one by one would
take an age.
Any
of large forms with 20+ fields, how should one go about coding
the wicket components? I have a large form of over 300 fields divided into
20 pages to code. Instantiating and wiring up each of these one by one would
take an age.
Any ideas?
Many thanks,
CN
--
View this message
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
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
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
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
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
13 matches
Mail list logo
