I'm in the process of integrating Ext-JS into our Wicket application. So there are a number of questions, such as: What are your experiences of using wicket and ext together? Do these projects help at all, or do you rather roll a custom behavior each time? Is there some project that is not indexed by Google (see below)? Are there some fundamental problems one runs into when building more complex UIs?
I found two projects that provide an integration; - wicket-ext at http://code.google.com/p/wicket-ext/ - wicket-extjs-integration http://code.google.com/p/wicket-extjs-integration/ Neither of these is very active, but I'm hoping that some of you have experience with them. The wicket-ext project has lots of widgets already integrated, but I don't really understand the reason for creating two hierarchies; one of Components and one of Behaviors. It seems to me that mapping ext components onto wicket components should be sufficient; behaviors can then be added to provide services to the client-side code. The wicket-extjs-integration project is in its infancy, but has a lot of potential; it maps ext components directly onto wicket components, has been explicitly designed to do composition and even has a nice way of invoking ext client-side methods from server-side code. I also like the annotation-based configuration of the client-side components. I would like to continue work on the second approach, but would like to get some feeling for the task at hand first ;-) thanks, Frank -- Hippo Europe • Amsterdam Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20 522 4466 USA • San Francisco 185 H Street Suite B • Petaluma CA 94952-5100 • +1 (707) 773 4646 Canada • Montréal 5369 Boulevard St-Laurent #430 • Montréal QC H2T 1S5 • +1 (514) 316 8966 www.onehippo.com • www.onehippo.org • [email protected]
