On 2 nov, 00:43, nino ekambi <[email protected]> wrote: > Hello Thomas, > First thank you for your reply. > I just realised my mistake after i released the library yesterday that i > should nt hav remove your headers. My knowledge in software licensing is not > really that big. But i think i gave you all the credit for the main idea of > this project in one my post here. The intention was not definilty to steal > anything from you since i m not trying to make money and hav any credits out > of this. > I m changing the source code right now the puting your copyrights back. > Once again sorry for the inconvience. > Like i said in one of the post i just saw that u were not interested to work > on the project anymore so i started my own. I wrote you a couple of times > but u were not really answering me(i guess u are a busy man). > HTML5 is great but i think some things will npt work in the normal browser > event with html5(offline pdf or excel generation for example).
This would help: http://www.w3.org/TR/file-writer-api/ (among other APIs) > If i put the library under gpl is because a friend told me that the best way > the keep improvment in the community. I don't think it's compatible with Apache-licensed code however (as soon as you start copying/adapting it; only using it isn't a problem, it's a "bind by name" in Java, so it's not considered a "Derivative Work" (otherwise GXT wouldn't be GPL'd)). That's why I don't think too much about licensing and just pick the one of the project I'm basing my work on (Apache 2.0, the same as GWT, in this case). And given that you don't intend to make money out of it (contrary to, say, GXT), I'd recommend using Apache rather than GPL so anyone can use it any way they want (provided they following the licensing terms; item #4 of the Apache 2.0 license distributed in the COPYING file for instance ;-) ) If you haven't changed anything to JsCollections, maybe you'd have rather kept the "original" one (package name, etc. maybe even the jscollections.jar) Or actually maybe you shouldn't rather use JsArray<?> all over the place instead of "casting" from/to Java arrays as I did (Java arrays make it clearer that it's designed to be immutable; GWT's own lightweight collections –coming in GWT 2.2 I hope– would make it even clearer and better [1]). [1] http://code.google.com/p/google-web-toolkit/source/browse/branches/lwc-gwt-migration/bikeshed/super/com/google/gwt/collections/super/com/google/gwt/collections/ImmutableArray.java Also, I saw that you started copying the Adobe doc into the javadoc (in ServiceMonitor for instance); beware of copyrights and licensing terms here too! http://www.adobe.com/products/air/tools/sdk/eula/ """You may not modify the Build Tools, PFI Build Tools (except for files that are covered by third party licenses that allow you to do so), Documentation or the Runtime Software in any manner.""" """This agreement does not grant you the right to distribute the Build Tools, PFI Build Tools (except for files that are covered by third party licenses that allow you to do so), Documentation or Runtime Software.""" -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
