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
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 to do yet.
once more, got a code example?
in wicket its just:
SortableDataProvider dp=createdataprovider();
List<IColumn> cols=createcolumns();
add(new DefaultDataTable("id", cols, dp, pagesize)
3. IDE support - both Netbeans and Eclipse have good support for JSF...it'd
be nice if the tools supported the technology in Wicket (convenience
stuff).
I haven't tried the eclipse plugin but I'm not sure it would work well w/
a
MyEclipse enterprise project....and I do mostly EJB3.0 architecture.
unfortunately wicket not being limited to beans the ide support is hard to
implement. it has the same problems as swing gui editors and the code they
generated, roundtripping, etc
fwiw the plugin should work fine and makes a world of difference.
4. Databinding - sometimes it is nice to set it and forget it...and only use
components when you need it. This of course, is contrary to Wicket...and
differs too much conceptually to do anything about.
yeah, but dont forget you can create impls of idataprovider, or even
subclasses of datatables that encapsulate all this if you need to reuse it
in many places.
5. Seamless capability to go stateless.
yep, we might work on that, we might not. we do not see statelessness as a
good thing necessarily.
6. I can inject a session bean into a JSF 1.2 managed bean using an @EJB
annoation...quick and simple. I have to use JNDI lookups in Wicket...more
code to manage.
ah, but with very little work: wrapping that jndi lookup in an impl of
IFieldValueFactory you can do the same with wicket. in fact there is a new
project in wicket-stuff that does this :)
7. The "model" concept can be tricky in certain cases and isn't intuitive...
because it is so simple it is very flexible and powerful. unfortunately
because it is so simple it is also hard to understand as it has very few
constraints. dont think we can do anything about it if we want to keep it as
powerful as it is now.
-igor
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
