cl-opengl-devel

Download

cl-opengl-devel@common-lisp.net

October 2008

2 participants
2 discussions

Re: [cl-opengl-devel] How is work normally done on this project?
by raito＠raito.com 11 Oct '08

11 Oct '08

Quoting Luís Oliveira <luismbo(a)gmail.com>: > You'll have to be more specific. If you're looking for ideas, see this > thread: <http://thread.gmane.org/gmane.lisp.cl-opengl.devel/185> I think I can better explain what I was asking now. I wasn't asking about what work to do, I was asking about how to go about making sure that work gets in where it's supposed to go. In some projects, one emails patches directly to the maintainer, who takes over from there. In some projects, one emails patches to the development list, and the maintainer takes it from there, but others might use rejected patches on their own. In some projects, everyone is given access to source control, and just throws stuff in (a rather wild and wooly version of development, but it exists). And that's aside from the process by which it's decided what paches go in or don't go in to official versions. Sometimes the maintainer decides, sometimes there's a committee, sometimes everyone just throws stuff in, etc. I'd like to 'play nice', but 'nice' means different things in different places. I'd like to know what 'nice' means for cl-opengl. For example, I've seen some patches submitted via this list, and I've seen you say 'thanks, I've put it in.' I've done some work on one of the items suggested (that being Redbook examples), and I'd like to see them get put into the 'official' stuff (realizing, of course, that cl-opengl doesn't really have releases). That's why I posted checker.lisp to the list. So how do I go about getting into the darcs repository in a way that will keep everyone happy with me? Yes, I've used a lot of text here, but the answer I got before (while useful) didn't answer the question I was asking. I hope that this is clearer. Neil Gilmore raito(a)raito.com

2 1

[cl-opengl-devel] checker.lisp (Redbook example)
by raito＠raito.com 02 Oct '08

02 Oct '08

Well, I was already working on porting the redbook examples to Lisp (at least the ones that hadn't been done yet). And as Luis pointed out, doing that is on the list. So here's the first one, ported from checker.c. It's a texture-mapping example. I have some others that need cleaning up, because prior to updating my stuff, I had to do things like code-char key in keyboard, because that's just how it worked on the Mac. I have noticed that some of the redbook examples can't currently be ported, because cl-opengl doesn't offer all the functions yet. I wasn't able to use '(64 64) when creating the texture map, because I get this error: * (load "checker.lisp") ; in: LAMBDA NIL ; (SETF (AREF RET-VAL (+ BASE 1)) 255) ; --> SB-KERNEL:%ASET ; ==> ; RET-VAL ; ; note: deleting unreachable code ; (SETF (AREF RET-VAL BASE) 255) ; ==> ; (SB-KERNEL:%ASET RET-VAL BASE 255) ; ; caught WARNING: ; Asserted type VECTOR conflicts with derived type ; (VALUES (SIMPLE-ARRAY T (64 64)) &OPTIONAL). ; See also: ; The SBCL Manual, Node "Handling of Types" And I haven't included an update to examples.lisp -- it's just adding it to the list of examples, and examples doesn't actually run the examples unless you've already loaded them (I might work on that for the future). Neil Gilmore raito(a)raito.com

1 0