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
On Mon, Mar 4, 2013 at 9:24 PM, Joao S. O. Bueno gwid...@mpc.com.br wrote:
While GIMP 2.9 is thriving with lots of possibilities, one thing remain as
fact:
it is dead slow.
O'RLY?
I will defer to mitch whether it is wise to do this type of GIMP-wide
re-architecting as summer of code..
El 04/03/13 11:24, Joao S. O. Bueno escribió:
[snip]
So, we might as well start fleshing out what would be needed to get
lazy rendering done,
just to get it clearer for everyone, and maybe have one or more of the steps
needed for that as Summer of Code projects.
+1000!
While I was reading
El 04/03/13 11:24, Joao S. O. Bueno escribió:
possibly even clipped to 8bpp with dumb acelerated 8bpp GEGL operators
and no conversion needed
Here I don't agree. In my opinion 8bpc should be only available for file
I/O. I wouldn't mind even if it's removed from the precision menu :D
Gez
On Mon, Mar 4, 2013 at 11:51 PM, Guillermo Espertino (Gez) wrote:
Considering the current performance in GIMP 2.9, this should be a top
priority task
It already is. There are two major todo items for 2.10:
1. Better performance.
2. Porting plug-ins to GEGL.
Alexandre Prokoudine
