From tpapp at Princeton.EDU  Sat May 16 01:51:27 2009
From: tpapp at Princeton.EDU (Tamas K Papp)
Date: Fri, 15 May 2009 21:51:27 -0400
Subject: [cl-cairo2-announce] syntax change in cl-cairo2
Message-ID: <20090516015127.GA5341@pu100877.student.princeton.edu>

Hi everyone,

I pushed a new version of cl-cairo2 to the GIT repository
http://github.com/tpapp/cl-cairo2/tree/master where it is kept now.

The most important change is that I disposed of the *context* global
variable, and moved context to the first argument, so now you write

(move-to context 0 -2)

instead of

(move-to 0 -2 context)

or

(setf *context*)
(move-to 0 -2)

I know this is an important change in syntax, and may break a lot of
code.  I apologize for the inconvenience, but this has been a major
wart on the initial design and I have always wanted to fix it.

Best,

Tamas



From tpapp at Princeton.EDU  Sun May 24 16:10:57 2009
From: tpapp at Princeton.EDU (Tamas K Papp)
Date: Sun, 24 May 2009 12:10:57 -0400
Subject: [cl-cairo2-announce] syntax change in cl-cairo2
In-Reply-To: <20090516015127.GA5341@pu100877.student.princeton.edu>
References: <20090516015127.GA5341@pu100877.student.princeton.edu>
Message-ID: <20090524161057.GA3825@pu100877.student.princeton.edu>

Hi cl-cairo2 users,

Comments after this change have persuaded me to change the interface
to something similar to the old one (but with a keyword argument).  If
you are still using cl-cairo2, please let me know what you think by
commenting here:

http://tkpapp.blogspot.com/2009/05/cl-cairo2-interface-poll.html

Thanks,

Tamas

On Fri, May 15, 2009 at 09:51:27PM -0400, Tamas K Papp wrote:
> Hi everyone,
> 
> I pushed a new version of cl-cairo2 to the GIT repository
> http://github.com/tpapp/cl-cairo2/tree/master where it is kept now.
> 
> The most important change is that I disposed of the *context* global
> variable, and moved context to the first argument, so now you write
> 
> (move-to context 0 -2)
> 
> instead of
> 
> (move-to 0 -2 context)
> 
> or
> 
> (setf *context*)
> (move-to 0 -2)
> 
> I know this is an important change in syntax, and may break a lot of
> code.  I apologize for the inconvenience, but this has been a major
> wart on the initial design and I have always wanted to fix it.
> 
> Best,
> 
> Tamas