Hm, if this license is LGPL then the restrictions are stronger than it
is depicted. You cannot extend this library without making your code
also in LGPL and this might not be what you wanted if you are selling
your software. Even if you're developing for a client, you might want
to be careful -- your client might not appreciate getting software
that is licensed in LGPL.
Although the site says 'encourage' you should check out the full terms
of the LGPL license and also be aware how you are using it. For
example, using it the way Jason did in creating helpers might very
well make the helpers LGPL-licensed.
Of course if you're using this for running your own apps it's
perfectly fine, neither LGPL or GPL will touch you.
> Hi guys,
>
> Great to meet you guys!
>
> Regarding yesterday's presentation about Ext JS, here's the answer for the
> questions on licensing:
>
> From the LICENSE.TXT file:
>
> Ext is also available under the terms of the Open Source LGPL 3.0 license.
> You may use our open source license terms if you:
>
> Are using Ext in a commercial application that is not a software development
> library or toolkit, you will meet LGPL
> requirements<
http://www.gnu.org/licenses/lgpl.html#section4>and you do
> not wish to support the project
>
> If you are using this library for commercial purposes, we encourage you to
> purchase
> a commercial license. Please visithttp://
extjs.com/licensefor more
> details.
>
> Note the word "encourage". So freely use this library in your commercial
> project, but in the spirit of Open Source, do purchase it if you can. :-)
>
> Cheers,
> Michael
>