> The control isn't _required_, Dave.
Who's Dave? My name is David.
> If you have reservations about using a compiled version that contains
> the control and a source that doesn't, I suggest a offsite link to the
> compiled version _with_ the control and onsite links to source and
> compiled version _without_ it.
I have reservations about a GPL project containing non-GPL code or
tools. Plucker does not (and should/will not) ever require or contain any
components which require a license or that are not free. We've had a similar
discussion awhile back about the Windows code Dirk was developing related to
a DLL if I recall correctly.
ALL components required to build Plucker are GPL'd or free. Any
third-party tool can do what they wish, proprietary or not, however, the
Plucker project itself will not be able to accept those patches or additions
internally if they require proprietary components or code. Since I don't run
Windows, I'm not clear where your codebase sits in the scheme of things, but
it looks like it's a bit redundant with what Dirk has, no?
In any case, if you would like to include your code in the Plucker
project (i.e. in the cvs, linked in with releases, etc.) let's see if we can
find a free/open alternative to the resizing component you've chosen.
Without that, I think it can only remain external.
Comments anyone? Am I being too anal here?
/d
