If Ext is GPL, then only the Ext libraries need to be GPL.
If you have code referencing Ext - that is NOT Ext, and so that specific
code does NOT need to be GPL'd.
All this means is that when you distribute your apps (sell em, give em
away, etc.), you are obligated to include the source for Ext that you
used.
Shawn
Jake McGraw wrote:
Does it mean, that if I have PHP application, that uses javascript
under GPL3, I must release also PHP source?
AFAIK if you bundle something GPL everything will become GPL. This includes
your PHP source.
Just an FYI, this is only for non-commercial versions of ExtJS. I
suppose the logic here is that if you would like to use ExtJS without
paying for a commercial license and reap the rewards of an open source
application, you will have to make your software open source (quid pro
quo). You have a couple of options if you'd like to continue using
ExtJS:
1. Keep using versions prior to 2.1 without making any changes to your
existing code base.
2. Buy a commercial license, you won't need to make any changes to
your code base.
3. Use a GPL version of ExtJS, open source any of your code
(server/client) which directly references ExtJS, no changes to you
existing code base.
4. Use a GPL version of ExtJS, remove any direct references of ExtJS
from your code, develop an interface (a JSON message server?) which
doesn't directly reference ExtJS, use it as an intermediate with
ExtJS. Using this method, you wouldn't need to open source any of your
software because you aren't directly referencing ExtJS.
Granted, none of this is as convenient as an MIT or BSD or LGPL or CC
license, but then, the core team ExtJS has a right to license their
software anyway they'd like to keep the project up and running.
- jake
