Re: [Pysdl-devel] pysdl & numpy decision

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

> so anyways, a decision has to be made. i personally
> still
> like the X,Y notation, it just 'clicks' for my
> brain. but
> i could easily adapt to the other style. it's really
> simple to do on the "C" side either way we just need
> to
> make a choice.
> 
> i definitely leave this one open for discussion, i
> might
> have missed a good argument for/against either
> method.

just my 2c:

my instinct is that if surface.pixels[] 'directly'
operates on a numpy array, then it should be in the
regular format of a numpy array ([y,x]) even if that
feels wierd.  That way, once you figure out how numpy
arrays work, you won't be confused further (like I was
by your example :) .  

that said I think it might be great to define
functions that would operate on the array 'indirectly'
and that would offer the familiar
surf.some_method(info, (INT x, INT y, INT w, INT h))
format, or surf.setpixel((x,y),color) or whatever. 
There are all kinds of possibilities for that... But
the 'real' array I think should be unreversed and if
possible contiguous, also then it would be as close as
possible to the way (i think?) SDL surfaces are
stored, even a few % speedup is worth it and the
transfer is more elegant.  Also I actually think it's
easier to think about because it's the same as the
regular PySDL surface access.
 --P






__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/