[Gimp-developer] test email; ignore
Making sure that this address works before I send a long email; sorry for the noise --xsdg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Google Summer of Code 2011 - Project Ideas/Suggestions
LightningIsMyName lightningismyname at gmail.com writes: I'm starting this thread to list ideas for Google Summer of Code 2011, for the GIMP project. Since in the last year collecting ideas was done partially by the mailing list, let's try it again this year and keep most ideas here. Automatic layer Boundary management. In essence just let the program deal with layer boundary - expand it whenever a layer is moved so that you can ALWAYS paint on any area you wish. If there's some memory or files size issue, perhaps add some automatic layer cropping on save. I want to stress that such a feature is really, really, useful. I believe there are some cases (scripts, maybe?) in which manual layer boundary management is necessary, so it should be just an option or something that can be deactivated temporarily. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Google Summer of Code 2011 - Project Ideas/Suggestions
On Sat, Feb 12, 2011 at 11:31 PM, Liam R E Quin l...@holoweb.net wrote: On Sun, 2011-02-13 at 01:04 +0200, LightningIsMyName wrote: Integrate vector layers with gegl GEGL already has all the support for rendering vector layers, so it is a case of adding the code to deal with as part of the nodes in the projection. Thus doing work on this would not really be possible until compositing the layers using GEGL is the default (or only) way this is done by GIMP. Better HDR support - e.g. aligning layers, (I think there may be patents on the various hugin algorithms for combining images though) Through gsoc last year, GEGL already has operations to combine multiple exposures into a HDR image as well as operations for tonemapping HDR images to standard dynamic range. Thus this is a task mostly about integrating UI bits with GIMP, once the drawables in GIMP are (and are backed by) GeglBuffers. /Øyvind K. -- «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] Google Summer of Code 2011 - Project Ideas/Suggestions
On 2/13/11, LightningIsMyName wrote: Slicing tool One of the most requested features by web designers and/or interface designers, is the addition of a slice tool. Currently slicing images inside GIMP can only be done in grids (using guides and the guillotine action) and you can't split just one rectangle in the middle. For example, the following slice can not be achieved: --- ||| ||| ||| ||| -|| ||| --- Oh come on, just port Slice tool from gimp-sharp to GIMP. All it takes is rewriting from C# to C + cairofication. *Then*, additionally, someone could rewrite it to work on canvas and save the slicing info in XCF. That's all, really. Adaptive Image Cloning (aka Semaless Cloning) As already stated in #gimp, it's an awesome idea. You only forgot to link to the paper :) http://www.cs.huji.ac.il/~danix/mvclone/ Alexandre Prokoudine http://libregraphicsworld.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Google Summer of Code 2011 - Project Ideas/Suggestions
On 02/13/2011 12:04 AM, LightningIsMyName wrote: I'm starting this thread to list ideas for Google Summer of Code 2011, for the GIMP project. Since in the last year collecting ideas was done partially by the mailing list, let's try it again this year and keep most ideas here. Thanks for a good start on this Barak I would like to add: Port UI code to a non-low level language Hacking UI code in C is a resource eater for us, we should use C for quick and efficient pixel processing but not for creating buttons. It would be interesting to make changes to the GIMP codebase that would allow us for example write the Pointer Information Dialog in JavaScript. / Martin -- My GIMP Blog: http://www.chromecode.com/ Nightly GIMP, GEGL, babl tarball builds ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Google Summer of Code 2011 - Project Ideas/Suggestions
On Sun, 2011-02-13 at 15:57 +, Øyvind Kolås wrote: On Sat, Feb 12, 2011 at 11:31 PM, Liam R E Quin l...@holoweb.net wrote: On Sun, 2011-02-13 at 01:04 +0200, LightningIsMyName wrote: Integrate vector layers with gegl GEGL already has all the support for rendering vector layers, so it is a case of adding the code to deal with as part of the nodes in the projection. Thus doing work on this would not really be possible until compositing the layers using GEGL is the default (or only) way this is done by GIMP. Or is _a_ way available even if not the default. Better HDR support - e.g. aligning layers, (I think there may be patents on the various hugin algorithms for combining images though) Through gsoc last year, GEGL already has operations to combine multiple exposures into a HDR image as well as operations for tonemapping HDR images to standard dynamic range. Thus this is a task mostly about integrating UI bits with GIMP, once the drawables in GIMP are (and are backed by) GeglBuffers. So it would make a good project, and fits within the Grand Vision. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ On the Internet no-one can touch your feet. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] GEGL 0.1.6
GEGL (Generic Graphics Library) is a graph based image processing framework. GEGL provides a graph based API and framework to do demand driven, cached, non destructive image editing of larger than RAM images. Through babl it provides support for a wide range of color models and pixel storage formats for input and output. To build gegl-0.1.6 you will also need babl-0.1.4 Changes in this release: • Fixed a bugs in matting-levin that made GEGL halt due to errors detected by babl sanity code, this made 0.1.4 be unusable if you had all dependendency when building. • build/test improvements. • New operations: max-rgb, pixelise, motion blur • Added extension points for GeglBuffer to use external tile backends, allowing to plug-in alien tilebackends, for legacy GIMP tilemanager/Krita/OSM and similar. This release of GEGL was made possible by contributions from: Tobias Ellinghaus, Øyvind Kolås, Barak Itkin and Martin Nordholts Where to get GEGL: The latest versions of GEGL and it's hard dependencies babl and glib can be fetched from: ftp://ftp.gimp.org/pub/babl/0.1/babl-0.1.4.tar.bz2 ftp://ftp.gimp.org/pub/gegl/0.1/gegl-0.1.6.tar.bz2 ftp://ftp.gtk.org/pub/glib/2.20/glib-2.20.5.tar.bz2 The integrity of the tarballs can be verified with: sha1sum *.bz2 1abe98b11e67737b6f74d6993d45046eec93bcda babl-0.1.4.tar.bz2 27bedcfd077da7a6913b82966dbec904b22c121d gegl-0.1.6.tar.bz2 19e2b2684d7bc35a73ff94eb7fd15fc70cc6f292 glib-2.20.5.tar.bz2 Where to get more information about GEGL More information about GEGL can be found at the GEGL website, or by joining #gegl or #gimp on the irc network GIMPnet. /Ø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
