On Thu, Jun 26, 2008 at 4:33 PM, yahvuu <yahvuu@xxxxxxxxx> wrote: > On Thu, Jun 26, 2008 at 2:31 PM, Øyvind Kolås <pippin@xxxxxxxx> wrote: > Anyhow, implementing these filters as new operations solves the problem > for now. Having two kinds of gaussian blur seems awkward at first, but > it is a user choice which edges to blur and not GEGL's. > The filter pairs can be merged later on by implementing > one as a meta operation of the other or simply by an > option property like "preserve bounding box". > > I'll derive the new filters from GeglOperationEdgedAreaFilter if > no better naming comes up. For the filters probably: > gaussian-blur-edged, > box-blur-edged It is much better to extend GeglBuffer to have an abyss policy, this means that requests for pixels outside the define area gets read back as if they were smeared/mirrored (or like now all 0). After this the gaussian blur could be changed to not expand it's result rectangle beyond the original input, and still use the current easily managable code paths for the actual filtering. /Øyvind K. -- «The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ http://ffii.org/ _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
