[Openmcl-devel] GUI on MacOSX (was: Carbon should be easy)

[Hamilton Link]

Even nicer, why? To me Objective-C vs. C isn't really the issue so much
as feature availability since the goal is programming in lisp. I suppose
that's still a reason, since certain GUI features are pre-defined in
Cocoa but not in Carbon, but OpenMCL already has a C FFI and making a
(solid and mature) Obj-C FFI might take a while.

Not to say it isn't worthwhile, just that it might take some doing and
while we wait we can get plenty of benefit just with Carbon. It's
certainly worth having someone around that's thinking about (and
advocating) Cocoa.

h

Yannick Versley wrote:
> 
> I think it would be even nicer to have the Cocoa framework available in
> OpenMCL. Ideally, this would mean creating an interface for getting
> classes and sending messages, and realize the rest via dynamic conversion,
> possibly creating something similar to the already existing Java bridge
> (there is an opensource clone created by folks of the GNUstep project),
> even if it does not blend very well with the CLOS-style of object
> orientation more common with LISP.
> 
> just daydreaming,
> Yannick Versley
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel


_______________________________________________
Openmcl-devel mailing list
Openmcl-devel at clozure.com
http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel