Fortunately for you, you don't need to look deeply at the license to find that you probably can use the code in your situation without worrying about "giving away" your application. The source sharing aspects of the GPL are only triggered by distributing the application that includes GPLed software. If your application is only ever used in-house, then the application has never been distributed and therefore the source does not need to be "given away". Now if you are creating the application as a contractor, and intend to retain ownership of the application, you would be distributing it to the company you are writing it for and would have to license it under the GPL, though even in that case the only people you would be required to give the source code to would be that company, of course they would be perfectly in their rights to give the code away to someone else.

To quote the ExtJS open source FAQ http://www.extjs.com/products/license-faq.php#cannotdo

"You can download the code base, install it, and modify it as needed. If you modify the code, we encourage you to contribute it back to the Ext community by contributing your modifications under GPL v3 in the Ext forums. Additional information is available in the official GPL FAQ.

Please note that if you distribute your modifications, you will have obligations under the GPL v3."

And from the GNU GPL FAQ http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic

"Does the GPL require that source code of modified versions be posted to the public?

The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.

But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL.

Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you. "

Joe Lee

Aaron Bartell <aaronbartell@xxxxxxxxx> 01/19/2010 14:21 >>>
At the time they had the richest set of configurable widgets. I must admit
that it was a big oversight on my part to not digress into the license
details further. But who looks deeply at a GPL v3 open source license more
than skimming it on the dnu.org web page? I didn't before, but I will be
doing so from now on.

I am looking into Dojo and jQuery right now.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Tue, Jan 19, 2010 at 3:30 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:

What was the compelling reason to go with ExtJS? What there some widget
or plugin that was especially valuable or did you just like their
javascript implementation better?

Pete



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.