This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Corey Sweeney <corey@interaccess.com> wrote: > #1 in order to get the image into memory, would a framegrabber->guile > chunk of code have to be written in C? how is the framegrabber currently programmed? is its API available as a shared library? what does the .h file look like? guile can use shared libraries. you can use `libtool' to create such from C source. there is another tool (whose name escapes me) that processes .h files to produce glue C code. of course, you can always roll your own. > #2 in order to access the image once it's in memory, what type of > "sturcture" can be used for the image? could it be "bluffed" into looking > like a list of lists to the program? or should a real interface be made > for it, so pixels could be accessed by new guile commands that are really > written in C? the latter is preferable, although you may have to fight NIH from all sides. :-> i think you should ask the next question... > also, has GIMP already addressed these issues, and come up with data types > for this (actually their, but hopefully compatible) purpose? probably. people have interfaced GIMP primitives to Scheme, too, so its really like shopping early saturday morning (lots of choices). thi