Re: CCL Editor Extendability [Cocoa IDE v1 project]

On Feb 21, 2009, at 7:18 AM, Gail Zacharias wrote:
> At 2/21/2009 08:39 AM, R.Stoye wrote:
>> may be I can rewrite/update this using ccl in the near future?
>
> The answer is yes, just as your code below is a combination of Fred
> and Carbon, you could do this in CCL using a combination of Hemlock
> and Cocoa.  Hemlock is CCL's replacement for Fred and Cocoa is
> Apple's replacement for Carbon.  Hemlock has buffers and marks and
> all that (http://trac.clozure.com/openmcl/wiki/HemlockProgrammer),
> and it has display code written on top of Cocoa.  Event handlers are
> methods (they are methods defined by Cocoa, but they can be
> specialized in Lisp, due to CCL's Objective C bridge) and various
> display objects are instances (again originating in Cocoa but
> subclassable in Lisp).  The display code internals are not
> documented, but all the source is available.
>
> This is not to say that there isn't room for improvement -- there are
> all sorts of bits and pieces that are missing and/or could be done
> better.  But the big picture is all there and we just need to
> identify the most important bits and pieces and get down to work...

It would be beneficial if multiple third party developers can make  
extensions to the editor without conflicts. Being able to customize,  
specialize and patch the editor as usual is useful, but extensions  
made this way will quickly conflict with other extensions to the  
editor. I missed having multiple subscriber event notification and  
other predefined extension hooks in Fred.

-- Terje Norderhaug
_______________________________________________
info-mcl mailing list
[email protected]
http://clozure.com/mailman/listinfo/info-mcl