You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Frank van Lankvelt <f....@onehippo.com> on 2010/09/29 12:09:25 UTC
wicket and ext-js
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 • info@onehippo.com
Re: wicket and ext-js
Posted by Fabio Fioretti <wi...@gmail.com>.
Hi Frank,
Sorry for the late reply. We are currently migrating our main
application from Wicket 1.3 to 1.4 and contextually upgrading
ext-wicket. This might eventually be the right occasion to update the
project, though we are still targetting Ext 2.2.
With regard to behaviors and components, we felt it was useful to keep
them separate in spite of a small overhead, as it is always easy to
merge them but much more complicated to extract a behavior from a
component. Anyway, ext-wicket was born to help up support Ext-JS
components we found interesting for our applications, and not to
provide a clean and complete mapping of Ext features into Wicket.
Therefore, its architecture is far from perfect!
Is your integration effort moving forward?
Kind regards,
Fabio
On Wed, Sep 29, 2010 at 4:43 PM, Frank van Lankvelt
<f....@onehippo.com> wrote:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicket and ext-js
Posted by Frank van Lankvelt <f....@onehippo.com>.
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 <windom.macrosorch@gmail.com
> 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
> <f....@onehippo.com> 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 • info@onehippo.com
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
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 • info@onehippo.com
Re: wicket and ext-js
Posted by Fabio Fioretti <wi...@gmail.com>.
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
<f....@onehippo.com> 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 • info@onehippo.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicket and ext-js
Posted by Frank van Lankvelt <f....@onehippo.com>.
I haven't; the main reason being that we are using Ext-JS for another
application we're developing and we'ld like to limit the number of
technologies in our stack. We are already using a mix of custom developed
javascript functionality and some standard YUI 2 components.
A major motivation for moving to Ext is the large number of components it
has. Of course, these will all have to be integrated into Wicket
separately, but the hope is that a set of suitable helpers/abstractions can
help keep the development costs low.
cheers, Frank
On Wed, Sep 29, 2010 at 1:33 PM, Alexander Morozov <
alexander.v.morozov@gmail.com> wrote:
>
> Hi,
>
> the integration projects, you mention above, seems inactive for a long
> time.
> Is it critical for your project to use exactly the Ext-JS javascript
> framework ? Have you looked at WiQuery project (jQuery integration) ?
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/wicket-and-ext-js-tp2718664p2718787.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
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 • info@onehippo.com
Re: wicket and ext-js
Posted by Alexander Morozov <al...@gmail.com>.
Hi,
the integration projects, you mention above, seems inactive for a long time.
Is it critical for your project to use exactly the Ext-JS javascript
framework ? Have you looked at WiQuery project (jQuery integration) ?
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-and-ext-js-tp2718664p2718787.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org