Re: [Pysdl-devel] Python2C results

[Peter N. <pn...@ya...>]

That's no big surprise I guess -- what I read about
python2c made it sound like a work in progress and you
don't often get something for nothing.  I think Mark
was talking a while back about possibly adding
functions to enable integrating PySDL into C programs
for scripting -- probably a ways off if it happens,
but I guess this would allow much of a program to be
basically in Python but with the slowest parts moved
to C.  Anyway PySDL is really not that slow.  It
certainly can beat Director, and with hardware
acceleration it can be pretty fast.  Also I read that
the different threading makes Python 2.0 a lot faster
in Windows when not using threads, so maybe this will
help?  

Speaking of Director the new image object in Director
8 is almost identical to an SDL surface, blitting
syntax is basically the same except blits have an
optional last argument for 'ink effects' which let you
do different surface operations before copying to the
destination.  This kind of thing might be nice in
PySDL, maybe the scripting stuff would make this
feasible.

P.S. Pete do you have a version of pysdl with the
numpy surface transfer in it?  I've been wanting to
play with bump-mapping and other stuff but I'm lazy
about it when I know it will be super slow.  

--Peter

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/