Hi after a week brake I decide to resume python gnome documentation:
The document that I did was
+ Python Gnome tutorial
The other documents that should exist are
+ Python Gtk tutorial
(GTK v1.2 Tutorial of Tony Gale & Ian Main codemorphed to python)
+ Python Gnome/Gtk Reference
+ FAQ
I think that they should exist because I think that there are
a lot of python programmers that aren't literated in C.
Python Gnome tutorial status: 66.341%
====================================
The postscipt version works now, sorry for the bad ps generation.
Please don't print the apendices you'll be only killing trees!!!
The Python Gnome tutorial has several unfinished seccions:
Pygnome architecture
--------------------
I have read the code and think I understand 40% how the bindings are
done. The only way I will understand them completely is if I do some
bindings. I had the Gtkextext in mind. But the bindings architecture
is going to change. James wrote:
" At the moment I am investigating some ideas that will make pygtk
easier to maintain, smaller, easier to autogenerate the source of
and a few other things. It should also allow having one
PyObject <-> one GtkObject, which people have been wanting for a
long time, without circular reference problems.
The changes will be using the ExtensionClass code which is currently
maintained with zope. "
so perhaps I would be more productive if I tried to understand how
ExtensionClass works. I just read
http://www.digicool.com/releases/ExtensionClass
and can't say I understood it completly.... :-)
So the question is should I try to do the Gtkextext bindigs to
understand how the binding are done now or should I spend that time
studing the ExtensionClass.
Pygnome conventions
-------------------
I think this is a very easy and important thing to do.
A pygnome GnomeHello shouldn't take to much time and I will result
in a nice example. This should be exactly like the C GnomeHello but
without all the autoconf,libtool,etc.. fuss you need for C compiling.
Cool pygnome examples
---------------------
I want to put a modified version of my glogo explainig how the canvas
works. If anybody has a nice example that whe thinks would ilustrate
the use of a complex widget please mail it to me.
Python Gtk tutorial status = 0.0000000001928374%
================================================
I definitly must start doing this. It's just boring work but it
should be VERY USEFUL documentation. Judy if you are reading this
please send me all those beautifull examples you have translated.
Python Gnome/Gtk Reference status = (0-epsilon)%
================================
I stated to work on pygdoc so it could generate docbook sgml but
I wasn't very good at it and dind't spend much time on it. Anyway
it should be useless because James said:
"The idea is to move most of what is in gtk.py into the C part of
the package."
So pygdoc won't be usefull because it parses the python code.
But we could give some good use to Franois Pinard "pygtk reminder"
code. Franois if you are reading this please send me the code
for the pygtk reminder. I would modify it to generate sgml, we can
perhaps even read the __doc__ strings with this.
It would be nice if the C code had __doc__ strings, they would be
VERY helpfull for documentation and autodocumentation.
FAQ status = 0.35%
=================
I think we should start a FAQ some question that come to my mind are:
+ Why do I get a [_o] when I do a dir() to an instance ?
+ How can I see the list of object that are contained in a widget ?
+ How do I parse for parse the command-line for arguments ?
+ How do I allocate a GdkColor ?
If you think of some more interesting questions please let me
know. We could start a thread called "FAQ questions" and then I
would try to reply them as well as I could. Of course I wouldn't
be mad I you posted the relpy with the quetion.
Ok, well I will start work right away.
Daniel Kornhauser
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
