The plain LGPL has no field-of-use restriction.  The restriction added
in the Ext license present a few major problems:

1. The new license is no longer compatible with the plain GPL.  The
plain GPL (any version) does not permit additional restrictions on field
of use.

2. The new license would not be considered to be a free software license
by FSF, nor an open source license by OSI.  I can tell you this with
absolute certainty, since one of my duties when I worked for FSF was
evaluating licenses. 

3. The new license is confusing.  It says it's LGPL, but then gives up
on many of the most important characteristics of the LGPL. 

4. I have no idea what a "developer toolkit" is.   

Unfortunately, under these circumstances, I cannot recommend the use of
current versions of Ext.  I will be recommending that we peg ourselves
to the latest version of Ext which was available under the plain LGPL.
This is what

On Fri, 2008-03-28 at 18:40 -0400, Ext Licensing wrote:
> Hi David,
> 
>   Thank you for you interest in ExtJS.  Ext is licensed under the Ext
> License http://extjs.com/license.  To help our community understand
> our intentions, we refer to the LGPL and grant usage under the terms
> of the LGPL so long as the product is not a developer toolkit.  I hope
> this clears up any ambiguity.  I noticed that TOPP is an avid
> supporter of open source.  I hope that you find our restrictions
> reasonable enough to use ExtJS with your projects.  Please let me know
> if I can answer any more of your questions.
> 
> Warm regards,
> Abraham Elias
> 
> On Fri, Mar 28, 2008 at 5:33 PM, David Turner <novalis@...>
> wrote:
>         Is ext truly available under the LGPLv3, with no additional
>         restrictions?  Your licensing page[1] makes this very unclear.
>         
>         
>         
>         
>         
>         [1] http://extjs.com/license
>         
> 
> !DSPAM:4019,47ed7402106838362916074!