hi Fabio, good to hear it is in active use and development! There might be more users than you think; perhaps you can get them to voice their enthousiasm. Might help to find the time to publish the changes?
Concerning your example, some behaviors are definitively offered best as actual wicket behaviors. Tooltips, data stores, other services you need from the client. But I still wonder whether that justifies the overhead, considering the large number of components. Are there other motivations like, I could imagine, needing to subclass the FormComponent to be able to participate in form processing? thanks, Frank On Wed, Sep 29, 2010 at 3:45 PM, Fabio Fioretti <[email protected] > wrote: > Hi, > > I am one of the developers behind "wicket-ext". > > The project hasn't been updated lately even though it is still used, > maintained and developed behind closed doors. We stopped updating it > both because of lack of public interest (we have received only few > external contributions) and because of the fact that the Ext-JS > components we found most useful for our applications are already > supported (i.e. we currently have no real interest in driving the > endeavour further). In addition, we had no time to clean-up the latest > code to the extent of releasing it publicly. > > I can say that the integration was quite straightforward and Wicket > proved to work very well with Ext-JS; in particular, we found grid > components (GridPanel, GroupingView, etc.) extremely useful. > > The separation of Behaviors and Components hierarchies was a design > decision rooted in flexibility and actually inspired by Wicket: we > wanted to allow the application of Ext behaviors to standard Wicket > components. Just to give an example, think of a PersistentTip applied > to a Wicket TextField through a simple textField.add(new > ExtBaloonBehavior(model)). Why would you need a custom TextField for > that? > > Good luck for your integration effort and, should you decide to build > on top of wicket-ext, feel free to ask. > > > Cheers, > > Fabio Fioretti > > > On Wed, Sep 29, 2010 at 12:09 PM, Frank van Lankvelt > <[email protected]> wrote: > > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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]
