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)
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 PROTE
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 p
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
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.
How
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 i
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* distri
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 an
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.