Re: [Gimp-developer] Meaning of delay in screenshot plugin
Hi, I don't think the plug-in will be removed but I would like not to clutter the user interface again. The current UI seems to be more appealing and usable than what we used to have. Personally I tend to use the Screenshot functionality that is built into the GNOME desktop. The screenshot is just a keypress (Print, Alt-Print) away and importing it into GIMP is accomplished easily by dragging the preview onto the GIMP toolbox. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] improving bicubic interpolation
Hi, before you start attacking the bicubic interpolation routines, could you please have a look at the outstanding bug report for Lanczos: http://bugzilla.gnome.org/show_bug.cgi?id=167956 Would be nice to get this one closed finally. And we can't release 2.4 as long as it is still open. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] GEGL 0.0.10 released
GEGL 0.0.8 was missing a file sometimes needed in the build environment, thus GEGL 0.0.10 has been rushed out to replace it. What is GEGL? = GEGL is a graph based image processing framework offering non-destructive image processing and compositing on large images. GEGL is suitable for projects ranging from small one-off projects to interactive applications. New in GEGL 0.0.10 == The internal API has stabilized a bit more since the last release as well as gotten a couple of new capabilities. This release has focused on narrowing down and documenting the public API. A HTML API reference can be found at http://gegl.org/api.html as well as in docs/api.html in the downloaded tarball. Some of the other improvements in this release: - Internal caches for rendering (internal floating point projection) - API for iterative rendering - API for querying node connections. - improved hit detection (still only bounding boxes) - performance enhancements to frequently used code paths. - improved relative path handling in test app Contributors to this release: Kevin Cozens, Øyvind Kolås and Sven Neuman. Where to get GEGL = GEGL and it's dependencies babl and glib can be fetched from: ftp://ftp.gimp.org/pub/babl/0.0/babl-0.0.12.tar.bz2 ftp://ftp.gimp.org/pub/gegl/0.0/gegl-0.0.10.tar.bz2 ftp://ftp.gimp.org/pub/glib/2.12/glib-2.12.6.tar.bz2 The integrity of the tarballs can be verified with: sha1sum *.bz2 4c5b8fbf96363996efd8cddca12c9d78d15c014b babl-0.0.12.tar.bz2 ee6bab2518fe27b520c8aadbe4085e1018a7b81e gegl-0.0.10.tar.bz2 30cf64bc5c93d5fbba23ea00fb9270d29fb81f8d glib-2.12.6.tar.bz2 Where to get more information about GEGL Information about GEGL can be found at the GEGL website http://www.gegl.org/ -- «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
Re: [Gimp-developer] improving bicubic interpolation
Hi, On Sun, 2007-01-28 at 22:04 +0100, [EMAIL PROTECTED] wrote: In fact that's exactly what I am working on. If you look at my last post to the bug you linked above you will see I started a new bug since this one was getting too long, confused and mixing a number of issues. http://bugzilla.gnome.org/show_bug.cgi?id=363775 Sorry, but I am unable to follow your way of handling bug reports. If there's now a new bug that deals with remaining issues in bug #167956, why is the former not closed then? And why is the new bug not on the 2.4 milestone? 2) scale_region_no_resample() calculates offset tables effectively using (x + 0.5) . This would seem to be aimed at using the midpoint to scale down but has no meaning to scaling up. It's a nop. Using guint instead of gint for this data would also be more efficient. Sorry, but guint is never any more efficient than gint and it is likely to introduce bugs that are very hard to find. Please avoid the use of guint by all means. It should only be used when bit-fiddling is involved. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer