How is solved linking? In C++ I can't link statically my application into LGPL library, instead I need dynamic linking (dll, so, ...). How about qooxdoo toolchain? If I understand it correctly (just the terms) that dynamic linking will be qooxdoo.js and application.js, but qooxdoo toolchain creates static, single JS "application_with_qooxdoo.js".
I'm really interested how these LGPL restrictions are applied to javascript frameworks, especially qooxdoo. To be honest, I'm not fan of GPL, LGPL licenses (for me it's complicated for nothing), but this is my personal opinion of course:) Is there any person who can answer to this? - I have no problem with toolchain, this can be like gcc (it's gpl, but output is not gpl), just the resulting files. 2009/8/19 Andreas Ecker <[email protected]>: > Hi Jason! > >> I haven't touched QooxDoo in about 9-11 months because of other projects etc >> and when I was telling a colleague about how slick qooxdoo was and looked at >> the latest demo I was FLOORED! WOW! I for one am not into using Google or >> Yahoo for things like this. > > Great you (still) like it. ;-) > >> I think I'm going to use QooxDoo as my complete GUI solution for all my web >> apps that it "fits" and in particular, my Jegas Application Server's front >> end. > > That's even better. > >> Question #1: Is there a license issue with using QooxDoo on products I might >> sell? I'm under the imporession I should just make a link on my pages that >> say something that is linkable to qooxdoo like:: User Interface Created With >> qooxdoo (version) or something like this. Perhaps in the footer of each >> page. > > I'll try to put some more info, particularly about typical use cases, > onto the license page soon, http://qooxdoo.org/license. Here are just > some quick comments (this is no legal advice!): > > Commercial products (i.e. "selling") are fully supported by qooxdoo's > licenses. > > Since you're talking about an Application Server, I suppose you'd ship > some software to customers? This is unlike most users, which merely host > qooxdoo-based apps internally or publicly. You then need to focus on the > "distribution" aspect of the licenses, particularly LGPL: > > Details depend on what you actually distribute (library vs. app) and if > and what you changed in the lib, also how you package/combine both. > Basically, you don't have to put your own app code under the same > license, but any modifications to the library (i.e. qooxdoo) are to be > made available to others in a license compatible way. For that, you'd > need to be clear about the licensing, copyright, attribution, etc. > > Since qooxdoo is dual-licensed, you are free to choose between the LGPL > _or_ EPL. I don't advocate/prefer any of the 2 licenses, just note that > they share much of the same "spirit". > > So much for a short feedback on the subject. I won't be available til > next Mo., but I'd be happy to continue our conversation and help with > resolving any issues. > > Bye, > > Andreas > > -- > Andreas Ecker > Project Lead > http://qooxdoo.org > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
