Peter | 16 Jul 07:54

State of play?

I've been in a split world of real code in MCL and parallel threads 
of exploration in CCL for more than a year.  With news that Snow 
Leopard may not support PPC systems, I'm reminded that more G5 
hardware failure may make my lisp coding days on Mac problematic.

What news of progress with MCL?  Am I hearing echoes in a dark 
chamber of legacy ... (I can see the shadow of my pension (Symbolics 
iron) far down in there already).

Finding the art of falling in love with Hemlock a tab counter 
intuitive (not helped by Clozure's being elsewhere occupied than on 
their IDE at present).  But that and diving into the Cocoa labyrinth 
seem the only visible glimmers at the moment.  Or get more serious 
about Lispworks.

I've long felt that investment in pure CLOS and OpenGL might last a 
while before Apple and it's NeXT 6 shooter blow my investments out of 
the water.  But just now, even those anchors don't seem so safe 
(complexity and lack of robustness anywhere are not encouraging).

Alex, how is Open Agent Engine going?

Anyone care to review the state of play?
Or has everyone gone off into the iPhone SDK sandbox!
_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

(Continue reading)

Glen Foy | 16 Jul 16:15

Re: State of play?

On Jul 16, 2008, at 1:55 AM, Peter wrote:

> Anyone care to review the state of play?

The Clozure IDE is understandably a low priority.  Clozure, after all,  
is in the business of making money.

One solution would be to make the IDE a commercial product.  The  
compiler would remain free, but we would pay for active development of  
the IDE.

The IDE should be based on Fred, not Hemlock.  The view/event model  
should be similar, if not identical, to the MCL model.  The tools  
should be tightly integrated like MCL.

I don't see this happening unless we pay for it.

_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

Raffael Cavallaro | 16 Jul 16:58

Re: State of play?


On Jul 16, 2008, at 10:15 AM, Glen Foy wrote:

> One solution would be to make the IDE a commercial product.  The
> compiler would remain free, but we would pay for active development of
> the IDE.

I obviously can't speak to the financial side of this from Clozure's  
point of view, but I would like to go on record saying that I would be  
willing to pay for an improved IDE and support with cocoa issues.

regards,

Ralph

Raffael Cavallaro, Ph.D.
raffaelcavallaro@...

_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

Alexander Repenning | 17 Jul 00:38

Re: State of play?

We do have a proof of concept implementation of the Open Agent Engine (an OpenGL based simulation engine written in CL, http://www.agentsheets.com/lisp/OpenGL.html) for Clozure CL. To see the engine in action check out: http://www.cs.colorado.edu/~ralex/papers/PDF/AVI08demo.pdf but you need the Adobe viewer to watch the moves. The next step would be to redesign things to better align Cocoa and WinAPI to create a fully cross platform engine shedding its MCL flavored history -  at least the obsolete parts. 

We need cross platform OpenGL and GUI APIs. Keeping everything open source including the CL implementation we could see Clozure CL to be a good choice at one point but when is that point going to be here? It just seems to be hard to reach the tipping point. Is it all a question of giving money to Clozure? Maybe... but maybe it is also a question of reaching a better understanding of the Clozure associates versus developer interface. I feel there really would be enough good will and programming resources with the people on this list but if we are not better organized and work towards a better formulated goal we will never get there. Now we are in phase where there is a lot of good programming taking place with some interesting wrapper code for this and that. But all this bottom up programming is not aligned. We are in a state of program contribution anarchy. That may be fine for now but how to take the next steps? Unfortunately, I do not have answers. However, I do think if Clozure would just put in a bit more effort into defining the general framework (e.g., Easy GUI including a portable event handling model) perhaps then it would simpler for people to contribute and plug in their contributions into a well defined interface. 

alex


On Jul 15, 2008, at 11:55 PM, Peter wrote:

Alex, how is Open Agent Engine going?

Prof. Alexander Repenning


University of Colorado

Computer Science Department

Boulder, CO 80309-430


vCard: http://www.cs.colorado.edu/~ralex/AlexanderRepenning.vcf



_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl
Andrew Shalit | 7 Aug 23:46

Re: State of play?

On Jul 16, 2008, at 1:55 AM, Peter wrote:

> I've been in a split world of real code in MCL and parallel threads
> of exploration in CCL for more than a year.  With news that Snow
> Leopard may not support PPC systems, I'm reminded that more G5
> hardware failure may make my lisp coding days on Mac problematic.
>
> What news of progress with MCL?  Am I hearing echoes in a dark
> chamber of legacy ... (I can see the shadow of my pension (Symbolics
> iron) far down in there already).

I'm back from vacation and have some (hopefully) good news to share on  
this subject.  Clozure has gotten a contract to port significant  
portions of MCL to CCL running on Intel Macintoshes.  We're currently  
working on this, and making good progress.  When it's further along,  
the resulting "MCL-in-CCL" will be released as open source.

Now, there are some caveats: the singular goal of the contract is to  
get our client's large gui-intensive MCL application running on Intel  
Macs with as few source code changes as possible.  That goal is  
driving our implementation work.  MCL-in-CCL will support the features  
needed by this application.  Because the application is large, it will  
as a matter of course sweep along with it a good percentage of MCL GUI/ 
Macintosh functionality, including windows, dialogs, menus, etc.  But  
it won't get everything, some things will work differently, and some  
things won't work at all.  In particular, events may be handled  
somewhat differently, threading is handled differently (CCL has real  
preemptive threads), some obscure features (e.g. colored menu items)  
may never even be tested, etc.  Most MCL source code will require some  
updating to run, though we do have the goal of minimizing that.

The big thing that is not included in this project is the MCL IDE.   
Now, the MCL IDE is written in MCL and is built on all the stuff  
described above, so it might not be too much additional work to get it  
running.  But we don't really know at this stage.  It will hopefully  
be clearer when the project is further along.  At that point the  
question of how to proceed will be one for the community to decide.   
We'd be happy to finish the work on a funded basis, or it could be a  
community-developed open source project.

Of course, if anyone wants to help fund this development effort to  
make it more complete sooner, we'd be happy to talk with you about that.

A bit of background on how MCL-in-CCL is being implemented:  Generally  
speaking, we are proceeding by resolving differences in the MCL and  
CCL system call (nee "trap") interfaces, and then porting the MCL GUI  
libraries for windows, menus, quickdraw, etc to the resulting version  
of CCL.  The work is currently being done in CCL PPC-32, but it will  
be moved to CCL Intel-32 as that matures in the coming months.  This  
approach has the advantage of supporting all of the Carbon libraries  
that MCL has been using for many years.  Of course, it also has the  
disadvantages that come with Carbon and 32-bit computing: they  
represent yesterday's APIs rather than tomorrows, they are not cross- 
platform, etc.

Still, we expect MCL-in-CCL to be a very useful way to provide life- 
extensions to many existing MCL applications and MCL programmers.   
That gives us time to continue to explore the other options people  
have raised for getting a longer-term more forward-looking solution.

I'm happy to answer questions about this as much as I can.   
Unfortunately, I'm not the only Clozure person who is taking summer  
vacations, so there are some questions that I may not be able to  
answer for a few weeks until we're all back.  But I'll do my best.

Andrew Shalit
Clozure Associates

> Finding the art of falling in love with Hemlock a tab counter
> intuitive (not helped by Clozure's being elsewhere occupied than on
> their IDE at present).  But that and diving into the Cocoa labyrinth
> seem the only visible glimmers at the moment.  Or get more serious
> about Lispworks.
>
> I've long felt that investment in pure CLOS and OpenGL might last a
> while before Apple and it's NeXT 6 shooter blow my investments out of
> the water.  But just now, even those anchors don't seem so safe
> (complexity and lack of robustness anywhere are not encouraging).
>
> Alex, how is Open Agent Engine going?
>
> Anyone care to review the state of play?
> Or has everyone gone off into the iPhone SDK sandbox!
> _______________________________________________
> info-mcl mailing list
> info-mcl@...
> http://clozure.com/mailman/listinfo/info-mcl

_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

Glen Foy | 12 Aug 23:00

Re: State of play?

On Aug 7, 2008, Andrew Shalit wrote:

> Now, the MCL IDE is written in MCL and is built on all the stuff
> described above, so it might not be too much additional work to get it
> running. But we don't really know at this stage.  It will hopefully
> be clearer when the project is further along.  At that point the
> question of how to proceed will be one for the community to decide.
> We'd be happy to finish the work on a funded basis, or it could be a
> community-developed open source project.

I'll just offer my two cents:

MCL-in-CCL sounds terrific.  There are many MCL apps out there that  
people want ported to Intel.

But porting the MCL IDE based on Carbon libraries does not make sense  
to me.  Carbon may disappear at some point.  Apple pulls the plug on  
technologies whenever it suits their purpose.

A better strategy would be to complete EasyGUI and port Fred to  
Cocoa.  Then the IDE could be a community-developed open source  
project.  You don't have to be a compiler hacker to develop tools.   
Working on the IDE is definitely something many of us could do.  The  
MCL IDE would serve as inspiration for the initial design.

Having said that, it's a bit of stretch to expect Clozure to port Fred  
just out of the goodness of their heart.  They have already spent time  
and resources on Hemlock.  A new port needs to be a funded project.   
Otherwise, it's not going to happen.

We should think in terms of MCL's reincarnation, not life-support.
_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl


Gmane