On Tue, Jan 25, 2011 at 8:40 AM, Stephen Greenwalt wrote:

Where can I help? Here's an ultra-short overview of my background: * Have some extra time I could devote . . . but will wait to quantify that until I hear where you need help.

This happens from time to time, sometimes people actually have the time and capability to help, quite often they ask for help - consume time to get up to speed, and then nothing happens. To avoid wasting more time on a reply to this email as well as other requests via mail, IRC and other places I have started writing up a list of pointers about the current state of GIMPs refactoring to use GEGL and where help would be appreciated.

See http://gegl.org/contribute.html for this list.

/Øyvind Kolås.

«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

I'm trying to come up to speed on gegl and built the hello-world.c example from the examples directory. The text from that example doesn't show up on the output, although the mandelbrot zoom works wonderfully. Is there anything I can do to figure it out? Can someone point me toward something to read to understand where things are going on?

Patrick

On 02/07/2011 04:48 AM, Patrick Horgan wrote:

I'm trying to come up to speed on gegl and built the hello-world.c example from the examples directory. The text from that example doesn't show up on the output, although the mandelbrot zoom works wonderfully. Is there anything I can do to figure it out? Can someone point me toward something to read to understand where things are going on?

One thing you can do is to run with the env var GEGL_DEBUG set to "process". That will give some output on how things are processed in the graph. Does the output for the text node look weird?

/ Martin

On 02/06/2011 10:52 PM, Martin Nordholts wrote:

On 02/07/2011 04:48 AM, Patrick Horgan wrote:

I'm trying to come up to speed on gegl and built the hello-world.c example from the examples directory. The text from that example doesn't show up on the output, although the mandelbrot zoom works wonderfully. Is there anything I can do to figure it out? Can someone point me toward something to read to understand where things are going on?

One thing you can do is to run with the env var GEGL_DEBUG set to "process". That will give some output on how things are processed in the graph. Does the output for the text node look weird?

/ Martin

btw, forgot to say this is on Ubuntu using gegl and babl from git trunk and gcc 4.6
Could it be where it says:
Using cache for pad 'output' on "gegl:text 0x9017e90"

Here's one time through the loop:

For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:text 0x9017f38" have_rect = 0,0 130×13 For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:nop 'proxynop-input' 0x90179f8" have_rect = 0,0 512×384 For "gegl:text 0x9017e90" have_rect = 0,0 135×13 For "gegl:scale 0x9017d40" have_rect = 0,0 135×13 For "gegl:opacity 0x9017de8" have_rect = 0,0 135×13 For "gegl:translate 0x9017c98" have_rect = 1,1 137×15 For "gegl:over 0x9017bf0" have_rect = 0,0 512×384 For "gegl:nop 'proxynop-output' 0x9017b48" have_rect = 0,0 512×384 gegl_processor_set_rectangle() node = gegl:display 0x90178a8 rectangle = 0, 0 512×384
For "gegl:fractal-explorer 0x905a000" have_rect = 0,0 512×384 For "gegl:nop 'proxynop-input' 0x90179f8" have_rect = 0,0 512×384 For "gegl:text 0x9017e90" have_rect = 0,0 135×13 For "gegl:scale 0x9017d40" have_rect = 0,0 135×13 For "gegl:opacity 0x9017de8" have_rect = 0,0 135×13 For "gegl:translate 0x9017c98" have_rect = 1,1 137×15 For "gegl:over 0x9017bf0" have_rect = 0,0 512×384 For "gegl:nop 'proxynop-output' 0x9017b48" have_rect = 0,0 512×384 For "gegl:nop 'proxynop-output' 0x9017b48" have_rect = 0, 0 512×384 need_rect = 0, 0 512×384 result_rect = 0, 0 512×384 For "gegl:over 0x9017bf0" have_rect = 0, 0 512×384 need_rect = 0, 0 512×384 result_rect = 0, 0 512×384
For "gegl:nop 'proxynop-input' 0x90179f8" have_rect = 0, 0 512×384 need_rect = 0, 0 512×384 result_rect = 0, 0 512×384 For "gegl:translate 0x9017c98" have_rect = 1, 1 137×15 need_rect = 1, 1 137×15 result_rect = 1, 1 137×15
For "gegl:fractal-explorer 0x905a000" have_rect = 0, 0 512×384 need_rect = 0, 0 512×384 result_rect = 0, 0 512×384 For "gegl:opacity 0x9017de8" have_rect = 0, 0 135×13 need_rect = 0, 0 135×13 result_rect = 0, 0 135×13
For "gegl:scale 0x9017d40" have_rect = 0, 0 135×13 need_rect = 0, 0 135×13 result_rect = 0, 0 135×13
For "gegl:text 0x9017e90" have_rect = 0, 0 135×13 need_rect = 0, 0 0×0 result_rect = 0, 0 135×13
Using cache for pad 'output' on "gegl:text 0x9017e90" For "output" processing pad 'gegl:scale 0x9017d40' result_rect = 0, 0 135×13 For "output" processing pad 'gegl:opacity 0x9017de8' result_rect = 0, 0 135×13
For "output" processing pad 'gegl:translate 0x9017c98' result_rect = 1, 1 137×15
For "output" processing pad 'gegl:fractal-explorer 0x905a000' result_rect = 0, 0 512×384
For "output" processing pad 'gegl:nop 'proxynop-input' 0x90179f8' result_rect = 0, 0 512×384
For "output" processing pad 'gegl:over 0x9017bf0' result_rect = 0, 0 512×384 For "output" processing pad 'gegl:nop 'proxynop-output' 0x9017b48' result_rect = 0, 0 512×384

On 02/07/2011 01:33 PM, Patrick Horgan wrote:

On 02/06/2011 10:52 PM, Martin Nordholts wrote:

On 02/07/2011 04:48 AM, Patrick Horgan wrote:

I'm trying to come up to speed on gegl and built the hello-world.c example from the examples directory. The text from that example doesn't show up on the output, although the mandelbrot zoom works wonderfully. Is there anything I can do to figure it out? Can someone point me toward something to read to understand where things are going on?

One thing you can do is to run with the env var GEGL_DEBUG set to "process". That will give some output on how things are processed in the graph. Does the output for the text node look weird?

/ Martin

btw, forgot to say this is on Ubuntu using gegl and babl from git trunk and gcc 4.6
Could it be where it says:
Using cache for pad 'output' on "gegl:text 0x9017e90"

Yes maybe, caches don't always work like they should. If you disable that code, does it become better? You can also set a breakpoint in process() for text and see that the thread of execution looks reasonable when you single-step through the code.

/ Martin

On 02/07/2011 09:03 AM, Martin Nordholts wrote:

On 02/07/2011 01:33 PM, Patrick Horgan wrote:

On 02/06/2011 10:52 PM, Martin Nordholts wrote:

On 02/07/2011 04:48 AM, Patrick Horgan wrote:

I'm trying to come up to speed on gegl and built the hello-world.c example from the examples directory. The text from that example doesn't show up on the output, although the mandelbrot zoom works wonderfully. Is there anything I can do to figure it out? Can someone point me toward something to read to understand where things are going on?

One thing you can do is to run with the env var GEGL_DEBUG set to "process". That will give some output on how things are processed in the graph. Does the output for the text node look weird?

/ Martin

btw, forgot to say this is on Ubuntu using gegl and babl from git trunk and gcc 4.6
Could it be where it says:
Using cache for pad 'output' on "gegl:text 0x9017e90"

Yes maybe, caches don't always work like they should. If you disable that code, does it become better? You can also set a breakpoint in process() for text and see that the thread of execution looks reasonable when you single-step through the code.

I haven't figured it out, but have found that if I switch this:

gegl_node_link_many (mandelbrot, layer, display, NULL); gegl_node_connect_to (text, "output", layer, "aux");

to

gegl_node_link_many (text, layer, display, NULL); gegl_node_connect_to (mandelbrot, "output", layer, "aux"); g_printf("layer has aux pad: %d\n", gegl_node_has_pad(layer,"aux"));

I get the text, but not the mandelbrot, and the g_printf reports that layer does have the aux pad (of course it would have printed something on its own to tell me if the pad wasn't there).

Patrick