Re: wicket and ext-js
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.vanlankv...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket and ext-js
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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket and ext-js
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.moro...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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 • i...@onehippo.com
Re: wicket and ext-js
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.vanlankv...@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 • i...@onehippo.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket and ext-js
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.macroso...@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.vanlankv...@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 • i...@onehippo.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@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 • i...@onehippo.com
Re: Wicket and Ext JS integration
The licensing is a pain. We started using ExtJS when it was LGPL, then they switched to GPL. By then we were already invested, so we bought a commercial license -- kind of feel like we got suckered into that one. If I had a chance to do it again I would just use YUI. We use ExtJS on top of YUI. However, ExtJS is a good product, even though they made a poor licensing decision. The licensing problem is just a fact that we have to deal with now, so I'm trying to find out what the easiest path is for integrating ExtJS 2.2 with Wicket. If someone else has already done the effort or started the effort, then that would help. The amount of work involved in integrating ExtJS 2.2 with Wicket is part of our new web framework evaluation criteria. Thanks, Richard Allen On Wed, Oct 22, 2008 at 2:05 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: I thought there were a licensing issue! Could'nt just remember if it were the guy doing the wicket contrib or ext js.. Martijn Dashorst wrote: The GPL licensing of ExtJS is really a brain damage inflicting mess. Personally I would stay very far away from JS libraries that are GPL licensed (it is not clear how the viral aspect infects your server side code, possibly requiring you to ship your server side code to your users—you *are* distributing the GPL licensed code, which is linked to your product) Martijn -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket and Ext JS integration
I could be interested to share experience about that, but now I'm really in early stage so I think it would be too early to share the code. Anyway the main idea is to use the Wicket behaviour feature to attach an Ext component to the associated Wicket component. This is the easiest part. More complex integration like Data Store could be always done using a Wicket ajax behavior. But I' haven't yet tryed to integrate more complex stuff like editable grids, groups and so on . . Paolo On Thu, Oct 23, 2008 at 1:41 PM, Richard Allen [EMAIL PROTECTED]wrote: The licensing is a pain. We started using ExtJS when it was LGPL, then they switched to GPL. By then we were already invested, so we bought a commercial license -- kind of feel like we got suckered into that one. If I had a chance to do it again I would just use YUI. We use ExtJS on top of YUI. However, ExtJS is a good product, even though they made a poor licensing decision. The licensing problem is just a fact that we have to deal with now, so I'm trying to find out what the easiest path is for integrating ExtJS 2.2 with Wicket. If someone else has already done the effort or started the effort, then that would help. The amount of work involved in integrating ExtJS 2.2 with Wicket is part of our new web framework evaluation criteria. Thanks, Richard Allen On Wed, Oct 22, 2008 at 2:05 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: I thought there were a licensing issue! Could'nt just remember if it were the guy doing the wicket contrib or ext js.. Martijn Dashorst wrote: The GPL licensing of ExtJS is really a brain damage inflicting mess. Personally I would stay very far away from JS libraries that are GPL licensed (it is not clear how the viral aspect infects your server side code, possibly requiring you to ship your server side code to your users—you *are* distributing the GPL licensed code, which is linked to your product) Martijn -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket and Ext JS integration
Paolo, Is this an open source effort? What version of ExtJS are you using? If we were to choose to go with Wicket, we would be willing to contribute. Thanks, Richard Allen On Wed, Oct 22, 2008 at 10:20 AM, Paolo Di Tommaso [EMAIL PROTECTED] wrote: I'm working on a wicket-ext integration project. Until now I've done just really simple stuff, like simple TextField, DateField, TimeField, ComboBox, AutoComplete field and basic (static) grid elements. Though my implementation is trivial I would say that is really promising and I've not found any evident obstacle to a more complete integration. Paolo On Wed, Oct 22, 2008 at 1:53 PM, Richard Allen [EMAIL PROTECTED] wrote: We currently use Ext JS 2.2 (http://extjs.com) with Struts 1.x, and we are considering migrating to Wicket. I have seen on the mail archive that some people have integrated Wicket and Ext JS with mixed success. In particular, I found the wicket-tools-extjs project, http://www.wickettools.org/index.php/extjs-integrationm, which is version 0.1.0, published in February 2008. Is the wicket-tools-extjs project in active development or was that project abandoned? Is there any other significant work undergoing to integrate Wicket and Ext JS? Thanks, Richard Allen
Re: Wicket and Ext JS integration
Yes, I'm working for a no-profit organization and it could be an interesting option to release it as an OSS. Do you have any suggestion where the project could be hosted? Google code? and any idea about the licence? Thank you, Paolo On Thu, Oct 23, 2008 at 2:19 PM, Richard Allen [EMAIL PROTECTED]wrote: Paolo, Is this an open source effort? What version of ExtJS are you using? If we were to choose to go with Wicket, we would be willing to contribute. Thanks, Richard Allen On Wed, Oct 22, 2008 at 10:20 AM, Paolo Di Tommaso [EMAIL PROTECTED] wrote: I'm working on a wicket-ext integration project. Until now I've done just really simple stuff, like simple TextField, DateField, TimeField, ComboBox, AutoComplete field and basic (static) grid elements. Though my implementation is trivial I would say that is really promising and I've not found any evident obstacle to a more complete integration. Paolo On Wed, Oct 22, 2008 at 1:53 PM, Richard Allen [EMAIL PROTECTED] wrote: We currently use Ext JS 2.2 (http://extjs.com) with Struts 1.x, and we are considering migrating to Wicket. I have seen on the mail archive that some people have integrated Wicket and Ext JS with mixed success. In particular, I found the wicket-tools-extjs project, http://www.wickettools.org/index.php/extjs-integrationm, which is version 0.1.0, published in February 2008. Is the wicket-tools-extjs project in active development or was that project abandoned? Is there any other significant work undergoing to integrate Wicket and Ext JS? Thanks, Richard Allen
Re: Wicket and Ext JS integration
Paolo, I think wicket-stuff ( http://wicketstuff.org/confluence/display/STUFFWIKI/Wiki) would be the place to put the code. I would recommend the license be the Apache License, version 2.0. As I understand, that is OK with GPL, version 3 ( http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense), which is the license used by ExtJS version 2.1 and up. -Richard On Thu, Oct 23, 2008 at 9:29 AM, Paolo Di Tommaso [EMAIL PROTECTED] wrote: Yes, I'm working for a no-profit organization and it could be an interesting option to release it as an OSS. Do you have any suggestion where the project could be hosted? Google code? and any idea about the licence? Thank you, Paolo On Thu, Oct 23, 2008 at 2:19 PM, Richard Allen [EMAIL PROTECTED] wrote: Paolo, Is this an open source effort? What version of ExtJS are you using? If we were to choose to go with Wicket, we would be willing to contribute. Thanks, Richard Allen On Wed, Oct 22, 2008 at 10:20 AM, Paolo Di Tommaso [EMAIL PROTECTED] wrote: I'm working on a wicket-ext integration project. Until now I've done just really simple stuff, like simple TextField, DateField, TimeField, ComboBox, AutoComplete field and basic (static) grid elements. Though my implementation is trivial I would say that is really promising and I've not found any evident obstacle to a more complete integration. Paolo On Wed, Oct 22, 2008 at 1:53 PM, Richard Allen [EMAIL PROTECTED] wrote: We currently use Ext JS 2.2 (http://extjs.com) with Struts 1.x, and we are considering migrating to Wicket. I have seen on the mail archive that some people have integrated Wicket and Ext JS with mixed success. In particular, I found the wicket-tools-extjs project, http://www.wickettools.org/index.php/extjs-integrationm, which is version 0.1.0, published in February 2008. Is the wicket-tools-extjs project in active development or was that project abandoned? Is there any other significant work undergoing to integrate Wicket and Ext JS? Thanks, Richard Allen
Re: Wicket and Ext JS integration
I'm working on a wicket-ext integration project. Until now I've done just really simple stuff, like simple TextField, DateField, TimeField, ComboBox, AutoComplete field and basic (static) grid elements. Though my implementation is trivial I would say that is really promising and I've not found any evident obstacle to a more complete integration. Paolo On Wed, Oct 22, 2008 at 1:53 PM, Richard Allen [EMAIL PROTECTED]wrote: We currently use Ext JS 2.2 (http://extjs.com) with Struts 1.x, and we are considering migrating to Wicket. I have seen on the mail archive that some people have integrated Wicket and Ext JS with mixed success. In particular, I found the wicket-tools-extjs project, http://www.wickettools.org/index.php/extjs-integrationm, which is version 0.1.0, published in February 2008. Is the wicket-tools-extjs project in active development or was that project abandoned? Is there any other significant work undergoing to integrate Wicket and Ext JS? Thanks, Richard Allen
Re: Wicket and Ext JS integration
The GPL licensing of ExtJS is really a brain damage inflicting mess. Personally I would stay very far away from JS libraries that are GPL licensed (it is not clear how the viral aspect infects your server side code, possibly requiring you to ship your server side code to your users—you *are* distributing the GPL licensed code, which is linked to your product) Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket and Ext JS integration
I thought there were a licensing issue! Could'nt just remember if it were the guy doing the wicket contrib or ext js.. Martijn Dashorst wrote: The GPL licensing of ExtJS is really a brain damage inflicting mess. Personally I would stay very far away from JS libraries that are GPL licensed (it is not clear how the viral aspect infects your server side code, possibly requiring you to ship your server side code to your users—you *are* distributing the GPL licensed code, which is linked to your product) Martijn -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
