[Guile-sdl-devel] Re: Great minds think alike ;)

[Alex S. <fo...@de...>]

>>>>> "Joel" == Joel Smith <jo...@mo...> writes:

    Joel> I agree that it would be best to use the guile-sdl name and
    Joel> the sourceforge site. Of course I would be willing to give
    Joel> admin status to anybody who wanted it.

You've already taken the initiative and set things up, I see no reason
you shouldn't remain the admin.  But you should add Vikram and I as
developers, or joint admins if that's allowed.

    Joel> As Alex said my guile-sdl project has far less of the SDL
    Joel> API covered so I think it would be best to use one of the
    Joel> other two as a starting point for the merging. Which one I
    Joel> personally don't know.

I think Vikram has a cleaner directory/file structure, and better
autoconf checking, so I've started merging my own code into his
project, using his files but preferring all of my actual functions
where they're duplicated, since we should probably move away from the
gh_ interface.  Then we can grab Joel's doc strings and start using
the snarfer.

I'm using the latest guile from cvs (to be released as guile 1.6 RSN),
and I'd suggest we move to this.  It means moving to the latest
autoconf/automake/libtool to build it, though.

Other conflicts:

Colors: Joel and I are using a smob, Vikram is using straight numbers.
I think it's cleaner to use a smob, so you can set individual r/g/b
components, and use the same color object on different bpp surfaces.

Constants: The technique used by other guile modules (like guile-gtk)
is to treat these as symbols, and translate them coming in and out as
parameters.  logior-ed flags are passed as a list of symbols.  I took
a hybrid approach, where most constants were just numbers, but event
types and keysyms are symbols, so you can use them in case statements.
The intent was to change this so that everything but flags would be
symbols, holding off on flags since it's a lot of overhead to
translate a symbol list to a logior-ed value on primitive functions.
I'm certainly open to ideas here, though.

Modules: As it is now, (sdl mixer) is a separate module, and I'm
changing (sdl ttf) to be separate as well.  The real question is
whether subsystems should be separate, so if you only need video for a
program you can just (use-modules (sdl video)) without having to
initialize all the other functions and constants (including many
keysyms).

Apart from that we seem to be spot on in code agreement.  Let me know
what you think.

-- 
Alex Shinn <fo...@de...>
Lisper, Smalltalker, and all around poor speaker