Re: [Gimp-developer] Improving pygimp documentation

2013-03-30 Thread Joao S. O. Bueno
On 29 March 2013 23:01, Sean Munkel wrote: > After picking this up again I've run into a problem. I'm not really > sure how to get this to replace the current gimp.PDB with its wrapped > version. Am I correct in thinking that the best way to do this is to > rename the gimp.so C library to be _gimp

Re: [Gimp-developer] Improving pygimp documentation

2013-03-29 Thread Sean Munkel
After picking this up again I've run into a problem. I'm not really sure how to get this to replace the current gimp.PDB with its wrapped version. Am I correct in thinking that the best way to do this is to rename the gimp.so C library to be _gimp.so and then importing everything from there in a py

[Gimp-developer] Improving pygimp documentation

2013-03-06 Thread Sean Munkel
>>One >> way to get around this issue of __doc__ not being display is to >> actually create a regular python function for each procedure. Instead >> of using gimp.PDB you would have to wrap it in a class that will use >> its methods but hook into __getattr__. Inside of __getattr__ it would >> creat

Re: [Gimp-developer] Improving pygimp documentation

2013-03-06 Thread Joao S. O. Bueno
On 6 March 2013 19:19, Sean Munkel wrote: > The problem with that is that help() would not display the__doc__ for > the instance of PDBFunction, but will instead generate a generic > overview of the class itself. As far as I can tell this is because > help() doesn't recognize PDBFunction instances

Re: [Gimp-developer] Improving pygimp documentation

2013-03-06 Thread Sean Munkel
The problem with that is that help() would not display the__doc__ for the instance of PDBFunction, but will instead generate a generic overview of the class itself. As far as I can tell this is because help() doesn't recognize PDBFunction instances as functions (or routines as they're called in ins

Re: [Gimp-developer] Improving pygimp documentation

2013-03-04 Thread Joao S. O. Bueno
I am sorry - this is not the way to proceed. There is no GIMP's "built-in help" - GIMP_Python does use standard Python's help - and that should no tchange. What standard Python help does is to display the function signature, when available, and the contents of the object's __doc__ attribute. Your

[Gimp-developer] Improving pygimp documentation

2013-03-03 Thread Sean Munkel
I know that the documentation of pygimp itself is a bigger priority than this, but I've been experimenting with a way to dynamically generate the documentation for procedures based on the metadata that they have. It automatically converts the parameters to the correct python type (though admittedly