| Newsgroups |
gmane.comp.video.fresco.devel |
| Message-ID |
<[email protected]> |
some comments to your license complaints:
you said, nobody could adapt fresco to portable
devices because it would need major changes.
as it is now, either portables have to become
more powerful (fpu) to be usable with the current
code, or you'd have to rewrite most of berlin
(our fresco implementation) anyway.
so maybe the IDLs should be under a less restrictive
license, but I'm not quite sure if they are "linked"
to anything, so that should as well be a non-issue
on the other hand I'll give you a different scenario:
think MegaCorp really likes the ideas of Fresco and
starts working on it (it's relicensed to WxWindows
license).
They write a big productivity suite for it
(closed source, no big deal with lgpl either) and
think that some widgets need to be adapted to their
needs...
so they modify their version of fresco which
they deliver with their operating system (that's
allowed with wxwin license), so it's API incompatible
with our fresco.
that's perfectly legal with wxwin license, but not with
lgpl. if they want to do that now, they'd have to resort
to subclassing into their own kits or something like that
which is fine - the base system is still compatible.
so the corporate developers that you highly praise didn't
gain us much except a cluttered space - no thanks
the wxwin license might be good for wxwin, as it's usually
linked directly into the applications - nobody cares which
calls are implemented there. once you export an API (that's
basically all fresco does), you have to be more careful to
protect it
oxygene
--
In mathematics, it's not enough to read the words
you have to hear the music