I'm embarking on a major rewrite of the PyGTK tutorial (http://www.moeraki.com/pygtktutorial) and would appreciate some feedback on the shortcomings and areas for improvement especially from a new PyGTK user.
Thanks
John
Dan Christian wrote:
On Monday 24 March 2003 06:43, Michael McLay wrote:
Do you think it would be harmful to put the PyGtk package into the
standard distribution prior to it being documented?
YES!
The problems with Tkinter that you mentioned were always a black eye for Python acceptance. Proposing another (semi) official GUI that isn't any better (on this front) simply won't help.
One of the ongoing problems is this idea of, "just check the Tk/Gtk docs and then convert". This has made it much harder for me to get started with PyGtk (and before that, with Tkinter). The mapping from C to Python is not always obvious and finding which module contains a feature can be difficult. By the way, this is a major problem with the wxPython documentation, too.
You really want to have a complete set of docs that stands independently from the underlying library. Maybe you maintain this automatically using the Gtk documentation, but the reader shouldn't have to know that. There should at least be an authoritative reference manual and a mature programmers guide/tutorial.
Sorry if this is a bit flamish, but I'm a new PyGtk user (as are most people), and I've wasted a lot of time trying to extract the right information from the PyGtk and Gtk documentation. It has gotten better, but there are still a lot of undocumented widgets and a lot of dark corners.
-Dan
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
