Frank Goenninger | 2 Dec 20:35 2007
Picon

UTILS-KT: Latest CVS updates: "ide" causes problems ...

Hi Kenny,

I just updated from CVS and found several challenges. The most  
intriguing is the IDE related stuff in several files (core, detritus).

As there are now some functions that are only meaningful when running  
on AllegroCL and when having the IDE in the image I'd like to know  
what the IDE pushes on *features* to make these functions only being  
there when Allegro and IDE are available.

Do you know what the magic #+(allegro ide) or some such string would  
be ? Thx!

Frank

Hi Kenny,

I just updated from CVS and found several challenges. The most  
intriguing is the IDE related stuff in several files (core, detritus).

As there are now some functions that are only meaningful when running  
on AllegroCL and when having the IDE in the image I'd like to know  
what the IDE pushes on *features* to make these functions only being  
there when Allegro and IDE are available.

Do you know what the magic #+(allegro ide) or some such string would  
be ? Thx!

(Continue reading)

Frank Goenninger | 3 Dec 11:46 2007
Picon

Re: UTILS-KT: Latest CVS updates: "ide" causes problems ...


Am 03.12.2007 um 00:09 schrieb Ken Tilton:

> Frank Goenninger wrote:
>> Hi Kenny,
>> I just updated from CVS and found several challenges. The most   
>> intriguing is the IDE related stuff in several files (core,  
>> detritus).
>> As there are now some functions that are only meaningful when  
>> running  on AllegroCL and when having the IDE in the image I'd  
>> like to know  what the IDE pushes on *features* to make these  
>> functions only being  there when Allegro and IDE are available.
>> Do you know what the magic #+(allegro ide) or some such string  
>> would  be ? Thx!
>
> Yes, that is it, but ISTR it should be #+(and allegro ide). Check  
> me on that. Thx for cleaning up.

Check. I was a bit sloppy in the email - it's correct in the source.

Frank


Am 03.12.2007 um 00:09 schrieb Ken Tilton:

> Frank Goenninger wrote:
>> Hi Kenny,
>> I just updated from CVS and found several challenges. The most   
(Continue reading)

Frank Goenninger | 3 Dec 13:32 2007
Picon

Cells: file variables.lisp: No more needed?

Hi again:

While trying to make cells.lpr and cells.asd consistent I noticed  
that there is file variables.lisp which is no more loaded from  
cells.lpr. Is it still needed or is it obsolete? I'd like to make  
Cells 3.0 as clean as possible as I am basing now more and more apps  
on it ... ;-)

Thanks for feedback.

Frank

Hi again:

While trying to make cells.lpr and cells.asd consistent I noticed  
that there is file variables.lisp which is no more loaded from  
cells.lpr. Is it still needed or is it obsolete? I'd like to make  
Cells 3.0 as clean as possible as I am basing now more and more apps  
on it ... ;-)

Thanks for feedback.

Frank

Andy Chambers | 5 Dec 14:59 2007

cello installation instructions

Hi,

What's the latest instructions for getting cello up and running?  The
install-notes in cvs refer to files and dlls that don't exist in the
repo.  Also it says to use the cells included but there is no cells
included.  Is there another repo/zip somewhere that is better to start
from?

I saw some stuff in the mailing list about people porting to cmucl.
Did anything come of that in the end?  I'd like to try to get it
working on sbcl/linux so any pointers would be appreciated.

Cheers,
Andy
Frank Goenninger | 6 Dec 11:34 2007
Picon

Re: cello installation instructions

Am 05.12.2007 um 14:59 schrieb Andy Chambers:

> Hi,
>
> What's the latest instructions for getting cello up and running?  The
> install-notes in cvs refer to files and dlls that don't exist in the
> repo.  Also it says to use the cells included but there is no cells
> included.  Is there another repo/zip somewhere that is better to start
> from?
>
> I saw some stuff in the mailing list about people porting to cmucl.
> Did anything come of that in the end?  I'd like to try to get it
> working on sbcl/linux so any pointers would be appreciated.
>
> Cheers,
> Andy

Hi Andy -

roughly (!) the following steps worked for me:

Part I: Sound

1. Get OpenAL (www.openal.org), compile, and install it.

Part II: Fonts

1. Get FreeType (http://www.freetype.org/freetype2/index.html),  
compile, and install it.
2. Get FTGL (http://ftgl.wiki.sourceforge.net/), compile, and install  
(Continue reading)

Ken Tilton | 6 Dec 16:09 2007
Picon

Re: cello installation instructions

Frank Goenninger wrote:
> Am 05.12.2007 um 14:59 schrieb Andy Chambers:
> 
>> Hi,
>>
>> What's the latest instructions for getting cello up and running?  The
>> install-notes in cvs refer to files and dlls that don't exist in the
>> repo.  Also it says to use the cells included but there is no cells
>> included.  Is there another repo/zip somewhere that is better to start
>> from?
>>
>> I saw some stuff in the mailing list about people porting to cmucl.
>> Did anything come of that in the end?  I'd like to try to get it
>> working on sbcl/linux so any pointers would be appreciated.
>>
>> Cheers,
>> Andy
> 
> 
> Hi Andy -
> 
> roughly (!) the following steps worked for me:

Very nice!

> 
> Part I: Sound
> 
> 1. Get OpenAL (www.openal.org), compile, and install it.
> 
(Continue reading)

Frank Goenninger | 6 Dec 16:39 2007
Picon

Re: cello installation instructions

Am 06.12.2007 um 16:09 schrieb Ken Tilton:

>> Part VI: Cello (finally ...)
>
> Do we need to pull down the Tcl/Tk Togl widget at this point? I  
> also grabbed Snack, or I think I did, not sure if that turned out  
> be part of the standard distro. Ah, then there is Tile, again not  
> sure if that is standard now.

Ah - right, the Togl stuff comes from http://togl.sourceforge.net/  
and should be installed as a step in Part III.

>> 1. Get latest Cello (Cello 2.0) from CVS via anonymous access from
>>     common-lisp.net:22/project/cello/cvsroot co cello
>> 2. Locate the sub-directory ftgl-int and compile the C DLL/Library  
>> in  there
>> 3. Locate all *config* files and adapt path names given in there  
>> for  your environment
>> 4. Load Cello via ASDF.
>> Now you should be there. If there is any "How do I do this ?" in  
>> the  list above I might warn you that this whole process easily  
>> can take a  week when doing it the first time (it took me four  
>> weeks to get a  clean build when first porting Cello to Linux in  
>> 2003).
>
> At one point it was possible to divide and conquer the overall  
> effort by first getting the demo in cl-opengl to run, than in any  
> order cl-ftgl and cl-magick and cl-openal, and then finally run the  
> lighting panel.

(Continue reading)

Peter Hildebrandt | 11 Dec 14:57 2007
Picon

Something like a def-family-observer?


Here's a question for you cells wizards out there (and Kenny in  
particular):

Say, I have a model M that depends on the structure of a family tree.  One  
of M's slots is therefore depending on the root of the family tree: (c?  
root).  However, I want M to know about changes in the family tree, like,  
say, when a child or grandchild is added.  Apparently cells (at least the  
cells_2.0 branch required by cells-gtk) does not broadcast change messages  
to the parents of a node (which I guess is the right thing in 99% of the  
cases).

What's the best way to deal with that?

(i) Is there some mechanism for this purpose present in cells? Or
(ii) Do I roll my own special case solution? Or
(iii) Is it worthwhile to build some general purpose solution to this  
problem?

My approach towards (ii) (I haven't coded anything yet, waiting for you  
comments) would be something like building an observer tree each node of  
which observes one node in the family tree.  Something like this:
- Design a tiny tree observer model ("tto"?), suited to observing one  
family node
(defmodel tty (family) (observed observed-kids reports-to))

- Every tto knows about the parent model (M from above) and does the right  
thing when it sees a change (say, call a closure)
- If the observed nodes has kids, it instantiates tto kids of its own to  
match the kids of the observed tree
(Continue reading)

Frank Goenninger | 11 Dec 19:42 2007
Picon

gui-geometry: CVS missing file "geo-macros"

Hi Kenny,

apparently you re-arranged some code in gui-geometry. Now I see there  
is a file "geo-macros" referenced in the .lpr file which does not  
appear in the .asd file. This may explain why I can't find stuff like  
^lr-width any more ... Could you please check this? Thx!

Frank

Hi Kenny,

apparently you re-arranged some code in gui-geometry. Now I see there  
is a file "geo-macros" referenced in the .lpr file which does not  
appear in the .asd file. This may explain why I can't find stuff like  
^lr-width any more ... Could you please check this? Thx!

Frank

Ken Tilton | 11 Dec 21:03 2007
Picon

Re: Something like a def-family-observer?

Peter Hildebrandt wrote:
> 
> Here's a question for you cells wizards out there (and Kenny in  
> particular):
> 
> Say, I have a model M that depends on the structure of a family tree.  
> One  of M's slots is therefore depending on the root of the family tree: 
> (c?  root).

More below, just retro-inserting notes: normally in /my/ work the parent 
slot is not even a Cell, but I /have/ done that a couple of times on 
certain subclasses of Family and it did work.

>  However, I want M to know about changes in the family tree, 
> like,  say, when a child or grandchild is added.  Apparently cells (at 
> least the  cells_2.0 branch required by cells-gtk) does not broadcast 
> change messages  to the parents of a node (which I guess is the right 
> thing in 99% of the  cases).

Confused: The kids slot is a Cell, so any rule anywhere (on slots not 
just the ascendants) that references (kids <whatever>) will get kicked 
off whent that changes. More below on this.

> 
> What's the best way to deal with that?
> 
> (i) Is there some mechanism for this purpose present in cells? Or
> (ii) Do I roll my own special case solution? Or
> (iii) Is it worthwhile to build some general purpose solution to this  
> problem?
(Continue reading)


Gmane