I think I will echo Eelco in wishing you all the best with Struts2.
Only thing I could summarize from this mail chain is that, maybe Wicket
needs that one extra out-of-the-box extension of ListView that you can do
say addColumn(String) and will use a Label by default?
Otherwise as I said earlier, it is a waste of time trying to reverse
pre-conceived notions about which is *THE* UI framework to use. Or if you
can point out anything obvious that the docs or examples are missing, I
guess that can be looked into as well.
Thanks,
Peter.
On 6/6/07, Florian Hehlen < [EMAIL PROTECTED]> wrote:
Hi John,
John Krasnay wrote:
> Amongst Wicket's many advantages, the following stand out for me:
>
> - The ability to encapsulate UI components, including all required
> markup, CSS, Javascript, and localization files, into shared JARs on
> the classpath. Having a shared component library is key to our team,
> since we tend to develop many small Web apps.
>
> - The ability to aggregate smaller components into larger and more
> complex ones. This allows us to create much richer pages, since we can
> think at an appropriate level of abstraction: I can just throw our
> standard page banner component on a page without thinking about the
> fact that it contains a logo, the app title, and a list of global
> navigation links. (In fact, it's even simpler than that. The banner is
> added by the base page that each app page extends.)
>
> - The fact that the same principles of a component tree and markup
> inheritance work from the smallest components right up to the entire
> page. This is very different from most Model2 frameworks, where you
> need something like SiteMesh or Tiles to add common banners and
> navbars to pages, and from JSF, where the internal structure of
> components is very different that the way they are composed into
> pages.
>
I agree with you that these are some of the strongest benefits of
Wicket. In my experience these facts were seen as a disadvantage... and
I am still trying to figure out why? My group is a very strong OOP group
yet the fully contained component advantage of Wicket was not appealing.
The only reason I can find for these irrational conclusion is that the
Model 2 frameworks out there have defined themselves as THE proper web
implementation of MVC.
Furthermore, our need for web-apps are peripheral to our main business.
We typically need to put together many small support web-applications.
so, Having a re-usabble set of components which require zero-config
would have been a great advantage.
florian
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
