| SWT API Copyright question [message #12207] |
Wed, 19 January 2005 11:10  |
Eclipse User |
|
|
|
Hello All.
Hope that this is the right newsgroup.
For a project I'm working on, I have developed a set of classes that
resembles the SWT classes (hierarchy, class names, method names, etc.)
but are used to generate html pages. Since I found these classes very
useful, I want to release them to the open source community.
Am I allowed to do such a thing ? Are the SWT class names, method names
and, in general, how they work toghether copyrighted in a way that I'm
not allowed to do a similar work ?
My classes are not using any code derived from the original SWT code and
of course the package names are different.
Bye
|
|
|
| Re: SWT API Copyright question [message #12215 is a reply to message #12207] |
Wed, 19 January 2005 14:58  |
| Eclipse User |
|
|
|
Marco,
The EPL (Eclipse Public License) happily allows you extend the APIs,
reimplement the APIs, use the libraries, etc. In fact, as long as you have
not changed the SWT code and re-released it (or incorporated the SWT code in
your released code), then you are free to release your code under any
license you want. We, of course, think you should use the EPL, but then
we're just biased :-)
Have you considered contributing your code to the SWT team to see if they'd
like to consider it for the base SWT releases?
Regards,
Bjorn Freeman-Benson
"not a lawyer and I don't play one on TV either"
|
|
|
| Re: SWT API Copyright question [message #12218 is a reply to message #12215] |
Wed, 19 January 2005 15:13 |
| Eclipse User |
|
|
|
On 19/01/2005 20.58 Bjorn Freeman-Benson wrote:
> The EPL (Eclipse Public License) happily allows you extend the APIs,
> reimplement the APIs, use the libraries, etc. In fact, as long as you have
> not changed the SWT code and re-released it (or incorporated the SWT code in
> your released code), then you are free to release your code under any
> license you want. We, of course, think you should use the EPL, but then
> we're just biased :-)
Good, so I can replicate the SWT class hierarchy and functionality
without problems. I think that I'll release the library under the EPL.
> Have you considered contributing your code to the SWT team to see if they'd
> like to consider it for the base SWT releases?
I don't know if the SWT team may be interested, as I said the library
replicates the SWT class structure, but the output is html for builing
web applications, not for stand-alone GUIs.
Bye
|
|
|
| Re: SWT API Copyright question [message #12664 is a reply to message #12218] |
Thu, 20 January 2005 02:14 |
| Eclipse User |
|
|
|
Have you considered some variation of subclassing?
On the surface, what you are doing may conflict with SWT. While I realize
that your library will probably not be linked at the same time as SWT, I can
see corner cases where this could become a problem for build/release/install
processes.
"Marco Maccaferri" <macca@maccasoft.com> wrote in message
news:csmf0v$4ph$1@www.eclipse.org...
>
> On 19/01/2005 20.58 Bjorn Freeman-Benson wrote:
>
> > The EPL (Eclipse Public License) happily allows you extend the APIs,
> > reimplement the APIs, use the libraries, etc. In fact, as long as you
have
> > not changed the SWT code and re-released it (or incorporated the SWT
code in
> > your released code), then you are free to release your code under any
> > license you want. We, of course, think you should use the EPL, but then
> > we're just biased :-)
>
> Good, so I can replicate the SWT class hierarchy and functionality
> without problems. I think that I'll release the library under the EPL.
>
> > Have you considered contributing your code to the SWT team to see if
they'd
> > like to consider it for the base SWT releases?
>
> I don't know if the SWT team may be interested, as I said the library
> replicates the SWT class structure, but the output is html for builing
> web applications, not for stand-alone GUIs.
>
> Bye
|
|
|
Powered by
FUDForum. Page generated in 0.04598 seconds
Home