<span class="gmail_quote"></span><br><div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It's complex relative to my goal, which was to get something working
<br>in a day or less. :-)
</blockquote></span><div><br>Of course it is not one-day task. Remapping of Xlib function calls to Win32 <br>GDI is not trivial task.<br> </div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What's non portable about Pyrex? I picked it thinking it was as<br>cross-platform as Python. Not so? Maybe I need to take another look<br>at ctypes. I thought ctypes was primarily for wrapping pre-existing C<br>code, and Pyrex was better/easier if you wanted to write an extension
<br>module from scratch and didn't mind it being tied to Python.</blockquote></span><div><br> Drawing module uses Xlib or GDI or Aqua, i.e. pre-existing C code. Therefore <br>ctypes based implementation will be more flexible and doesn't require
<br>recompilation on each platform. It's a pure Python code without native part.<br></div><br>Igor.<br></div><br>