I don't see any problems for wxCL as 1. it has to change away from CLisp FFI anyway to reach widespread adoption (UFFI/CFFI),
2. they changed the license from GPL to LGPL. Hence, we are not trapped by GPL. Dwight Holman <[EMAIL PROTECTED]> wrote: > On 12/15/05, Clemens Fruhwirth <[EMAIL PROTECTED]> wrote: > > What about using wxCL as McCLIM backend? > > I am scared by certain issues with wxCL. Currently, it only works on > CLisp. While this isn't normally a stubling block, it seems that > large portions of the wxCL code use the CLisp FFI package. First of all, this has to be rewritten anyway. FFI conversion is usually not a hard thing to do. Another light task for a Gardener. UFFI is not hard to learn. Probably, we need CFFI (callbacks). CFFI is another project that we should accept into our software portfolio because it is an important component for Lisp adoption together with the approaching-with-giant-steps Verranzo/FetterFFI [1]. > This means wxCL is held to the GPL, and cannot be licensed as LGPL. wxCL is licensed under http://www.opensource.org/licenses/wxwindows.php, the license transitation was made between 1.0.0 Alpha and 1.1.0 Alpha. The wxwindows license is basically LGPL. > [1] Basing McCLIM on wxCL would then make McCLIM GPL, creating a big > licensing mess for the communities working on McCLIM currently. This is no option. [1] http://common-lisp.net/project/fetter/ Regards, Clemens -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: [EMAIL PROTECTED] _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
