"Franz Mueller" <[EMAIL PROTECTED]> wrote in message
9l9c1v$[EMAIL PROTECTED]">news:9l9c1v$[EMAIL PROTECTED]...
> So, a few (easy?) questions:
> - If I use the component as a "black box", i.e. just put the component on
> the form and react on the events, there should be no problem with MPL,
> should there?
Correct in my view
> - If I change the code directly, I have to give the changed code to
others.
> (SourceForge should be ok.)
Correct in my view
>
> One more difficult question:
> Let's assume a MPL class (C++, or Pascal) called "SynEdit" can work
together
> with another class, let's call it "THighlighter".
> Now I write a new Highlighter called "MyHighlighter". It must be a
> deriverate of "THighlighter", but is not based at all on the base class -
> except it has the same function names.
> But if I use commercial code in MyHighlighter, I've got a problem. But -
> what I could do is changing the SynEdit so that it also accepts
> MyHighlighter. Then I'd give the new SynEdit to public, so that everybody
> can use (under MPL) SynEdit now with a Highlighter not based on
THighlighter
> but on MyHighlighter - if they had it. But I keep MyHighlighter
proprietary.
>
> What about this one?
IIRC, there was a statement from someone not long ago that if you change the
original code to accommodate for your code, but the Original code will
function as before (i.e. you don't create a dependency on your code), then
you only have to publish the changes, but don't have to publish your
proprietary code.
So in the above scenario you should be OK.
The usual disclaimer, I am not a lawyer <g>
--
Michael Beck (Team JEDI) http://delphi-jedi.org
http://www.geocities.com/beckmi/delphi.htm
