On 9/28/06, James Bielman <[EMAIL PROTECTED]> wrote:
"Charlie Burrows" <[EMAIL PROTECTED]> writes:
> Also I sidestepped the whole image loading issue by putting all the
> image data (64x64x24 bits) into a lisp file. I'm open to
> suggestions.
One idea that might be worth looking into is loading the data into an
array at compile time using EVAL-WHEN. You can find the texture
relative to the source file by using *COMPILE-FILE-PATHNAME* (perhaps
falling back to *LOAD-PATHNAME* when loading the source).
This makes it easy to distribute textures as normal files but also
doesn't require the texture file when delivering an executable.
James
Cool I will give that a try tomorrow. I've been using cl for ~4 years
now and I still feel like I'm just scratching the surface. I like
that!
Cheers,
Charlie
_______________________________________________
cl-opengl-devel mailing list
cl-opengl-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-opengl-devel
