That's interesting. What are you going to use to display the output
of your python script, and how would that obscure the actual greybox
code?
Here's some text I found regarding a library called Ogre and the LGPL
- maybe that will make it clearer:
"Under the LGPL you may use Ogre for any purpose you wish, and modify
it if you require, as long as you:
1. Pass on the (modified) Ogre source code with your software, with
original copyrights intact
1. If you distribute electronically, the source can be a
separate download (either from your own site if you modified Ogre, or
to this site if you used an unmodified version) - just include a link
in your documentation
2. If you distribute physical media, the Ogre source that you
used to build your application should be included on that media
2. Make it clear where you have customised it.
The above is a precis, please do read the full license agreement.
There are a few specific details to point out:
1. When OGRE is dynamically linked (the default), anything you use
it in is not a derived work and thus you can license your own software
under any license you choose; the LGPL does not 'infect' your
software.
2. When OGRE is statically linked, your work becomes a derived work
of OGRE and is covered by the LGPL too. You must either release your
source, or include linkable object files of your work if you do this
3. The license mentions 'inlining' as potentially making the
software using it a derived work; however this is mostly an issue for
libraries which mostly comprise headers, like template libraries.
Inlining in OGRE is entirely for performance and is a small part of
the whole, and therefore any inlining of OGRE headers does not
constitute a derived work (so point 1 still applies)."
As for the email...the author may not care enough to answer :(
--
Tyler Style
http://malthusian-solutions.com
http://nirdvana.com
On Jan 17, 5:08 pm, ArqEco <[email protected]> wrote:
> Hi Tyler,
>
> It's not a javascript application. It's a python web application
> wrapped on clickable single executable file.
>
> I wrote to author but I am still waiting for his answer.
>
> Greetings,
> Márcio
>
> On Jan 15, 6:30 pm, Logos <[email protected]> wrote:
>
> > I *think* that so long as you don't modify it and keep the license and
> > credit information in the file then it is OK. However, if I was you
> > I'd email the author and ask him personally.
>
> > BTW, how do you plan to keep a Javascript application closed source?
> > No way to do that unless you're using a custom browser.
>
> > --
> > Tyler Stylehttp://malthusian-solutions.comhttp://nirdvana.com
>
> > On Jan 15, 8:17 am, ArqEco <[email protected]> wrote:
>
> > > I am a non-native english speaker and all that LGPL "legalese" is very
> > > hard to me understand.
>
> > > Please, I need a clear answer...
>
> > > Is it possible to useGreyBoxon acommercialclosed-sourcesoftware??? Take
> > > in account thatGreyBoxwill be used without any
> > > modification.
>
> > > Thank you,
> > > Marcio
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GreyBox" 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/greybox?hl=en
-~----------~----~----~----~------~----~------~--~---
