From asf at boinkor.net Sat Oct 1 15:05:18 2005 From: asf at boinkor.net (Andreas Fuchs) Date: Sat, 01 Oct 2005 17:05:18 +0200 Subject: [mcclim-devel] [patch] minor goatee improvements (arrow keys!) Message-ID: <871x35b7m9.wl%asf@boinkor.net> Hi all, I have here a patch to make arrow keys and the Home and End keys in a goatee input buffer DTRT. I'm not entirely sure if the patch to lookup-gesture-command is doing the right thing, so I'd like a CLIM gesture specialist to at least glance over it before I commit it. (: Here's the patch: -------------- next part -------------- A non-text attachment was scrubbed... Name: ,goatee-arrows.patch Type: application/octet-stream Size: 2733 bytes Desc: not available URL: -------------- next part -------------- Have fun, -- Andreas Fuchs, , asf at jabber.at, antifuchs From asf at boinkor.net Fri Oct 7 21:06:34 2005 From: asf at boinkor.net (Andreas Fuchs) Date: Fri, 07 Oct 2005 23:06:34 +0200 Subject: [mcclim-devel] Is anyone using McCLIM with :unicode on *features*? Message-ID: <874q7t11gl.wl%asf@boinkor.net> Hi all, short story: I wonder if anyone is using McCLIM on CLX with the :unicode feature. Please test with: (cl:member :unicode cl:*features*) and report non-NIL results to this list. Thank you! long story: while trying to refactor the CLX backend's medium implementation, I found a lot of #+unicode statements in Backends/CLX/medium.lisp. From the comments, it looks like they shouldn't even be there: ; Yes, the following is a nasty hack. ; It's just a proof of concept, I'll try not to commit it :] ; If it does get committed, it shouldn't affect anyone much... These definitions don't *seem* to me like they are used by anyone, so I'd like to nuke them in favour of definitions that have a chance of working with mcclim-freetype's idea of text-style properties without requiring an ugly hack (like the method redefinitions that mcclim-freetype currently employs). So, again, please test if you're using McCLIM with the feature :unicode. Run (cl:member :unicode cl:*features*) and report non-NIL results to this list. I may be breaking your McCLIM soon, and we don't want that to happen without a good reason (-: Thanks, -- Andreas Fuchs, , asf at jabber.at, antifuchs From strandh at labri.fr Sun Oct 9 04:53:56 2005 From: strandh at labri.fr (Robert Strandh) Date: Sun, 9 Oct 2005 06:53:56 +0200 Subject: [mcclim-devel] Is anyone using McCLIM with :unicode on *features*? In-Reply-To: <874q7t11gl.wl%asf@boinkor.net> References: <874q7t11gl.wl%asf@boinkor.net> Message-ID: <17224.41572.165913.637133@serveur5.labri.fr> Hello Andreas, Andreas Fuchs writes: > > short story: > > I wonder if anyone is using McCLIM on CLX with the :unicode feature. > Please test with: > > (cl:member :unicode cl:*features*) > > and report non-NIL results to this list. Thank you! I already answered you on #lisp, but for the record: That code is currently not in a usable state (it has references to a package named `external-format' and that is not in the McCLIM distribution. For that reason, I think it is safe to remove. That said, I think we will need something to replace it in order to get the fonts right when doing arbitrary Unicode stuff. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. --------------------------------------------------------------------- From m.retzlaff at gmx.net Thu Oct 13 15:13:40 2005 From: m.retzlaff at gmx.net (Max-Gerd Retzlaff) Date: Thu, 13 Oct 2005 17:13:40 +0200 Subject: [mcclim-devel] a patch for mcclim/Lisp-Dep/mp-acl.lisp Message-ID: <20051013151340.GB16173@mgr.home> Hello, what do you think about this patch for mcclim/Lisp-Dep/mp-acl.lisp? Index: mp-acl.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Lisp-Dep/mp-acl.lisp,v retrieving revision 1.5 diff -a -u -r1.5 mp-acl.lisp --- mp-acl.lisp 10 Mar 2004 12:03:45 -0000 1.5 +++ mp-acl.lisp 13 Oct 2005 15:25:07 -0000 @@ -30,8 +30,24 @@ (eval-when (:load-toplevel :compile-toplevel :execute) (pushnew :clim-mp *features*)) +#+nil (defun make-process (function &key name) (mp:process-run-function name function)) + +;; In ACL each process has its own dynamic enviroment, +;; therefore a special binding doesn't affect the global binding of +;; the variable and the new process doesn't see that special binding. +;; In other words: +;; (let ((*debugger-hook* #'clim-debugger:debugger)) +;; (clim-listener::run-listener :new-process t)) +;; does not work, if *debugger-hook* is not explicitly bound to +;; the current special binding for the new process. +;; mgr, 20050706 +(defun make-process (function &key name) + (mp:process-run-function `(:name ,name + :initial-bindings ((*debugger-hook* . ,*debugger-hook*) + , at excl:*cl-default-special-bindings*)) + function)) (defun destroy-process (process) (mp:process-kill process)) Regards, Max -- Max-Gerd Retzlaff For your amusement: You're currently going through a difficult transition period called "Life." -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tim at tenkan.org Sun Oct 16 18:14:47 2005 From: tim at tenkan.org (Tim Daly Jr.) Date: 16 Oct 2005 20:14:47 +0200 Subject: [mcclim-devel] [patch] fix apparent typos Message-ID: <87psq5cors.fsf@beer.intern> In my travels through the looking-pane, I bumped into these: -------------- next part -------------- A non-text attachment was scrubbed... Name: apparent-typos.patch Type: text/x-patch Size: 1074 bytes Desc: fix apparent typos URL: -------------- next part -------------- -- -Tim From d.lewis at gold.ac.uk Fri Oct 21 15:19:38 2005 From: d.lewis at gold.ac.uk (David Lewis) Date: Fri, 21 Oct 2005 16:19:38 +0100 Subject: [mcclim-devel] Resizing windows Message-ID: <55b90193c8fb27c88796c29a10ee4534@gold.ac.uk> Hi, Working with Christophe Rhodes on a lute tablature editor under Climacs, I'm using one basic climacs window and a graphical window created with open-window-stream: http://common-lisp.net/project/climacs/tabcode.png Because of the need to resize the graphical display as the text changes, I've put an allocate-space command into our redisplay routine. That seems to work, but resizing the window manually (with the mouse) seems to resize the stream rather than (as I expected it to) the viewport. Is that expected behaviour? Should I be approaching the problem differently? Thanks, David Lewis P.S. A side issue to this is that the scroll-bars seem not to refresh automatically. Should I be running a command to do that or is this a bug/feature? From jcrippen at gmail.com Fri Oct 21 22:42:47 2005 From: jcrippen at gmail.com (James Crippen) Date: Fri, 21 Oct 2005 12:42:47 -1000 Subject: [mcclim-devel] (statusp cocoa-port) Message-ID: What's the current status on the Cocoa backend for McCLIM? I have an all Mac environment now, and I'd like to hack on Climacs a bit. But I'd rather have it running in Cocoa than in X. Is the Cocoa port working, for some suitable value of working? Or is it basically dead? If the latter, what needs to be done to ressurect it? Thanks, James From amoroso at mclink.it Sat Oct 22 10:12:02 2005 From: amoroso at mclink.it (Paolo Amoroso) Date: Sat, 22 Oct 2005 12:12:02 +0200 Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: (James Crippen's message of "Fri, 21 Oct 2005 12:42:47 -1000") References: Message-ID: <871x2d7te5.fsf@plato.moon.paoloamoroso.it> James Crippen writes: > What's the current status on the Cocoa backend for McCLIM? I have an > all Mac environment now, and I'd like to hack on Climacs a bit. But > I'd rather have it running in Cocoa than in X. Is the Cocoa port > working, for some suitable value of working? Or is it basically dead? > If the latter, what needs to be done to ressurect it? If you mean the Beagle backend in Backend/beagle, Duncan Rose is working on it and you can find some information on its status in README.txt. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log From amoroso at mclink.it Sat Oct 22 10:32:37 2005 From: amoroso at mclink.it (Paolo Amoroso) Date: Sat, 22 Oct 2005 12:32:37 +0200 Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: (James Crippen's message of "Fri, 21 Oct 2005 12:42:47 -1000") References: Message-ID: <878xwl6dve.fsf@plato.moon.paoloamoroso.it> James Crippen writes: > What's the current status on the Cocoa backend for McCLIM? I have an Some Beagle-related entries from my blog: McCLIM changes: Beagle Backend, Freetype bindings, command processing http://www.paoloamoroso.it/log/050627.html McCLIM changes: Beagle backend and Freetype bindings http://www.paoloamoroso.it/log/050610.html McCLIM changes: font metrics, bounding, events in Beagle backend http://www.paoloamoroso.it/log/050529.html McCLIM changes: Beagle backend, incremental redisplay http://www.paoloamoroso.it/log/050518.html Update on McCLIM's Beagle backend http://www.paoloamoroso.it/log/040822.html Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log From duncan at robotcat.demon.co.uk Sat Oct 22 18:31:48 2005 From: duncan at robotcat.demon.co.uk (Duncan Rose) Date: Sat, 22 Oct 2005 19:31:48 +0100 Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: <871x2d7te5.fsf@plato.moon.paoloamoroso.it> Message-ID: <1B0BAF58-432A-11DA-9DCB-000A9577B8A2@robotcat.demon.co.uk> On Saturday, October 22, 2005, at 11:12 am, Paolo Amoroso wrote: > James Crippen writes: > >> What's the current status on the Cocoa backend for McCLIM? I have an >> all Mac environment now, and I'd like to hack on Climacs a bit. But >> I'd rather have it running in Cocoa than in X. Is the Cocoa port >> working, for some suitable value of working? Or is it basically dead? >> If the latter, what needs to be done to ressurect it? > > If you mean the Beagle backend in Backend/beagle, Duncan Rose is > working on it and you can find some information on its status in > README.txt. > I've been a bit lax of late unfortunately; the necessary changes wrt text sizing Christophe added to McCLIM haven't been implemented and none of the other changes since then have been tested. I don't think it should take much to get it back to the state it was in a while ago (i.e. working for most things but slow and buggy). -Duncan > > Paolo > -- > Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log > _______________________________________________ > mcclim-devel mailing list > mcclim-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel > From joswig at lisp.de Sat Oct 22 23:27:53 2005 From: joswig at lisp.de (Rainer Joswig) Date: Sun, 23 Oct 2005 01:27:53 +0200 Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: <1B0BAF58-432A-11DA-9DCB-000A9577B8A2@robotcat.demon.co.uk> Message-ID: Does it work with the released OpenMCL 1.0? It would cool if it would. Regards, Rainer > Von: Duncan Rose > Datum: Sat, 22 Oct 2005 19:31:48 +0100 > An: Paolo Amoroso > Cc: > Betreff: Re: [mcclim-devel] (statusp cocoa-port) > > > On Saturday, October 22, 2005, at 11:12 am, Paolo Amoroso wrote: > >> James Crippen writes: >> >>> What's the current status on the Cocoa backend for McCLIM? I have an >>> all Mac environment now, and I'd like to hack on Climacs a bit. But >>> I'd rather have it running in Cocoa than in X. Is the Cocoa port >>> working, for some suitable value of working? Or is it basically dead? >>> If the latter, what needs to be done to ressurect it? >> >> If you mean the Beagle backend in Backend/beagle, Duncan Rose is >> working on it and you can find some information on its status in >> README.txt. >> > > I've been a bit lax of late unfortunately; the necessary changes wrt > text sizing > Christophe added to McCLIM haven't been implemented and none of the > other changes > since then have been tested. > > I don't think it should take much to get it back to the state it was in > a while > ago (i.e. working for most things but slow and buggy). > > -Duncan > >> >> Paolo >> -- >> Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log >> _______________________________________________ >> mcclim-devel mailing list >> mcclim-devel at common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel >> > > _______________________________________________ > mcclim-devel mailing list > mcclim-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel > From duncan at robotcat.demon.co.uk Sun Oct 23 08:56:19 2005 From: duncan at robotcat.demon.co.uk (Duncan Rose) Date: Sun, 23 Oct 2005 09:56:19 +0100 Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: Message-ID: On Sunday, October 23, 2005, at 12:27 am, Rainer Joswig wrote: > Does it work with the released OpenMCL 1.0? It would cool > if it would. > I haven't tried McCLIM / Beagle / OpenMCL 1.0 together so I have no idea if it works or not. Perhaps somebody else has. Nor am I aware of any fixes that would sort out the problems running Beagle on Tiger throws out (last I heard Beagle did NOT work on 10.4). -Duncan > Regards, > > Rainer > From campbell at mumble.net Sun Oct 23 16:55:04 2005 From: campbell at mumble.net (Taylor Campbell) Date: Sun, 23 Oct 2005 16:55:04 +0000 (UTC) Subject: [mcclim-devel] (statusp cocoa-port) In-Reply-To: (duncan@robotcat.demon.co.uk) Message-ID: <20051023165504.A65D99802B@pluto.mumble.net> Date: Sun, 23 Oct 2005 09:56:19 +0100 From: Duncan Rose I haven't tried McCLIM / Beagle / OpenMCL 1.0 together so I have no idea if it works or not. Perhaps somebody else has. Nor am I aware of any fixes that would sort out the problems running Beagle on Tiger throws out (last I heard Beagle did NOT work on 10.4). I haven't tried OpenMCL 1.0, but Beagle definitely did work on Tiger, at least until Christophe Rhodes introduced the TEXT-BOUNDING-RECTANGLE stuff that broke it: ...although it took several tries and about an hour to make that image. But it works, albeit very slowly and flakily. From smustudent1 at yahoo.com Sat Oct 29 03:45:34 2005 From: smustudent1 at yahoo.com (C Y) Date: Fri, 28 Oct 2005 20:45:34 -0700 (PDT) Subject: [mcclim-devel] Spec license? Message-ID: <20051029034534.42215.qmail@web31703.mail.mud.yahoo.com> As long as I'm looking into this in other projects, I might as well ask here - what are the copyright/license terms of the CLIM spec? Cheers, CY __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs