V. Jenks wrote:
Sure, I'd be happy to comment on that.
Some constructive criticism; there are many things that JSF does easier
and/or better (IMO) than Wicket.
1. select lists are *much* easier to populate, manipulate, and deal with. ;)
It is possible that our DropDownChoice looks a bit
1. select lists are *much* easier to populate, manipulate, and deal with. ;)
2. paging and sorting tables/grids/lists are *much, much* easier to
implement, something I wish would be made easier in Wicket. I'd do it
myself if I had time...and tried in the past...but am just not skilled
enough
1. select lists are *much* easier to populate, manipulate, and deal with. ;)
Could you write some pseudo-code (or real code) that is simpler than
the current implementation? I.e. what steps in the current
implementation can be streamlined?
2. paging and sorting tables/grids/lists are *much,
What about a StatelessPage (1.3 2.0) that had a Visitor that checked
whether any of its components were not stateless?
I think that should work by default now. So if all components on a
page are stateless, the page will be recognized being stateless and
thus not be put in the session. Correct
first, you dont need to specify that IChoiceRenderer as it does what the
default one does
second, you are doing this: form.add(new DropDownChoice(phoneType, new
Model(),
that newModel() isnt bound to your entity, so use a constructor without that
IModel param - that way the compound property
offtopic, would like to hear about your jsf experience compared to wicket.
anything you found better that we can improve?
-igor
On 1/10/07, V. Jenks [EMAIL PROTECTED] wrote:
Hi all, been a long hiatus for me but I'm diving back into Wicket finally.
I'm a little rusty (was forced, against
Sure, I'd be happy to comment on that.
Some constructive criticism; there are many things that JSF does easier
and/or better (IMO) than Wicket.
1. select lists are *much* easier to populate, manipulate, and deal with. ;)
2. paging and sorting tables/grids/lists are *much, much* easier to
One more thing :D
Wicket has a fantastic group of developers and the support has been
top-knotch...the same can't be said about every project.
If this mailing list wasn't here I might not have used Wicket so much...or
at all.
igor.vaynberg wrote:
offtopic, would like to hear about your jsf
That worked, thanks a lot.
igor.vaynberg wrote:
first, you dont need to specify that IChoiceRenderer as it does what the
default one does
second, you are doing this: form.add(new DropDownChoice(phoneType, new
Model(),
that newModel() isnt bound to your entity, so use a constructor
cool, thanks for the comparison, a few points to discuss
On 1/10/07, V. Jenks [EMAIL PROTECTED] wrote:
1. select lists are *much* easier to populate, manipulate, and deal with.
;)
can i have an example of code?
2. paging and sorting tables/grids/lists are *much, much* easier to
10 matches
Mail list logo
