From celestialcognition at gmail.com Sun Oct 3 22:49:30 2010 From: celestialcognition at gmail.com (Benjamin Caplan) Date: Sun, 3 Oct 2010 17:49:30 -0500 Subject: [cl-opengl-devel] Documentation Message-ID: Does the documentation not exist yet, or am I just failing to generate it correctly? From luismbo at gmail.com Mon Oct 4 00:02:10 2010 From: luismbo at gmail.com (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=) Date: Mon, 4 Oct 2010 01:02:10 +0100 Subject: [cl-opengl-devel] Documentation In-Reply-To: References: Message-ID: On Sun, Oct 3, 2010 at 11:49 PM, Benjamin Caplan wrote: > Does the documentation not exist yet, or am I just failing to generate > it correctly? It doesn't exist yet. Cheers, -- Lu?s Oliveira http://r42.eu/~luis/ From tomsict at gmail.com Thu Oct 14 20:53:19 2010 From: tomsict at gmail.com (Tomislav Tomsic) Date: Thu, 14 Oct 2010 22:53:19 +0200 Subject: [cl-opengl-devel] Hi to all :). Does anyone else have problems with ASDF2 and cl-opengl? Message-ID: This being my first message here, greetings to you all :). I've just updated my sbcl on version 1.0.48.58,, and cl-opengl doesn't work. I am using it via clbuild on the Ubuntu 10.04 (64). This is the error message: 0: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) ..) 1: ((SB-PCL::EMF ASDF:PERFORM) # # # #) 2: ((SB-PCL::FAST-METHOD ASDF::PERFORM-WITH-RESTARTS (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) ..) and so on. As I am able to discern, thanks to the numerous tries with various sbcl versions, yesterday and today, suddenly there is a problem with the file/resource locking, during the compilation. According to the sbcl documentation, that "feature" is in somewhat volatile state, and is the responsibility of the client software. To cut the story short, I think it is because of the new ASDF 2, that sbcl is starting to ship with. As such, I trust it will be resolved, sooner or later. In the meantime, does anyone have an idea for a workaround? Perhaps all that is needed is a slight change in the cl-opengl.asd, but I have no idea which one. At this moment, I am both unfamiliar with the newest asdf, as well as with the cl-opengl architecture. Once again, greetings to you all :) Respectfully Tomislav Tomsic From loliveira at common-lisp.net Fri Oct 22 14:31:04 2010 From: loliveira at common-lisp.net (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=) Date: Fri, 22 Oct 2010 15:31:04 +0100 Subject: [cl-opengl-devel] Fwd: CL-OPENGL has conflicts with Alexandria In-Reply-To: References: Message-ID: -- Lu?s Oliveira http://r42.eu/~luis ---------- Forwarded message ---------- From: "Nikodemus Siivola" Date: 14 Oct 2010 06:32 Subject: CL-OPENGL has conflicts with Alexandria To: "Oliver Markovic" , "Luis Oliveira" < loliveira at common-lisp.net> I just added #+sbcl (:lock t) to Alexandria's package definition. Turns out CL-OPENGL has the following conflicts: STARTS-WITH ONCE-ONLY ROTATE Cheers, -- Nikodemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikodemus at random-state.net Thu Oct 28 11:58:29 2010 From: nikodemus at random-state.net (Nikodemus Siivola) Date: Thu, 28 Oct 2010 14:58:29 +0300 Subject: [cl-opengl-devel] Using idle events to drive Slime Message-ID: I define (defmethod glut:idle ((window glut:window)) (swank::process-requests t)) to keep Slime responsive while the event-loop runs (when running single-threaded) -- which is nice enough, but a tad inelegant not just because of the double-colon, but because it causes __every__ window to call PROCESS-REQUESTS. I'm wondering if there should be a single global *IDLE-HOOK* (or maybe REGISTER-IDLE-HOOK) in addition to the per-window method approach -- something which causes windows to automatically subscribe to Idle events without registering themselves in *WINDOWS-WITH-IDLE-EVENTS*. Cheers, -- Nikodemus