I decided to scrap the python and go with the C interface to GTK. Learning PyGTK first certainly made it easier. I'm still struggling with a few things but I think the code will be cleaner this way. Good thing is that I can use the same glade xml file that I used with PyGTK.
Pyrex looks convenient but I frequently modify the C code. That would require translating to Pyrex every time I make changes. On Feb 17, 2008 9:41 AM, Maximilian Wilson <[EMAIL PROTECTED]> wrote: > 2008/2/17 Jeff Bullard <[EMAIL PROTECTED]>: > > I briefly looked at the html document called "Python/C API reference > manual" > > on the python.org site. That looked very painful. If it is that hard I > > think I may be better off rewriting the GUI using the C interface to > GTK. > > Please advise me on the best approach. > > Don't use the raw API. Use Pyrex (or Boost/Python if you don't mind > C++) for interfacing between C and Python. > > Sorry for the short reply. Thoughts on PyGTK/C interface some other time. > > -Max > > > -- > "The presentation or 'gift' of the Holy Ghost simply confers upon a > man the right to receive at any time, when he is worthy of it and > desires it, the power and light of truth of the Holy Ghost, although > he may often be left to his own spirit and judgment." --Joseph F. > Smith (manual, p. 69) > > Be pretty if you are, > Be witty if you can, > But be cheerful if it kills you. >
_______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
