Re: Review of public GEGL API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On 12/4/06, Øyvind Kolås <pippin@xxxxxxxx> wrote:
>> >    2. The term "bounding box" is clearer than "defined region". > 
>> >       *gegl_node_get_bounding_box
>>
>> The names of the concept internally, and a decision externally
>> might be propagated to the inside as well. Another option might be
>> gegl_node_get_bounds , or with a naming choice more similar to the
>> ones used by cairo, gegl_node_get_extents.
>
> I've renamed this one to gegl_node_get_bounding_box for now,
> I think gegl_node_get_dirty_rect should be renamed to be more similar
> to gegl_node_get_bounding_box.

I like

gegl_node_get_bounding_box
gegl_node_get_bounding_box_of_dirt
gegl_node_clear_dirt

the most.

I think dirt is a good word, at least better than uncomputed. It both 
makes sense and is easier to write.

- Martin N.
_______________________________________________
Gegl-developer mailing list
Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer


[Index of Archives]     [Yosemite News]     [Yosemite Photos]     [gtk]     [GIMP Users]     [KDE]     [Gimp's Home]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux