Re: [Gimp-developer] tiff save dialog cosmetic fix
Hi, Dov Grobgeld [EMAIL PROTECTED] writes: Speaking of tiff files, is there any particular reason why the tiff plug-in doesn't support saving multiple layers as tiff pages, or is it just that noone has got around to implementing it? Before you even think about doing any changes to the TIFF plug-in, can we please at least consider to switch to the TIFF plug-in written by Kai-Uwe Behrmann. We didn't do this for 2.0 because it was proposed too late but now would be a good time for it. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Lists, Arrays and Vectors [was Re: [Gimp-developer] Re: Tiny-Fu: A new plug-in for GIMP]
Hi, Kevin Cozens [EMAIL PROTECTED] writes: Script-Fu scripts written for GIMP 1.2 won't work under GIMP 2.x without some changes due mainly to differences in the API. In what version of GIMP would it be possible to have the compatibility features of Tiny-Fu removed? The next time we release a version that doesn't guarantee backward compatibility. This will most probably be called GIMP 3.0 then. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] saving multi-page TIFF files [was: tiff save dialog cosmetic fix]
Hi, Dov Grobgeld [EMAIL PROTECTED] writes: Speaking of tiff files, is there any particular reason why the tiff plug-in doesn't support saving multiple layers as tiff pages It may be a misunderstanding of the TIFF format but I don't think that GIMP layers map very well to TIFF pages. If we would make the TIFF plug-in save layers as pages, that would be rather confusing and a lot of users will end up with multi-page TIFF files they never intended to create. IMO multiple pages in TIFF files are a rather obscure feature that should be left for FAX applications. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] tiff save dialog cosmetic fix
Hi, Brion Vibber [EMAIL PROTECTED] writes: While I was playing with the tiff plugin, I fixed it to disable the 'Save color values from transparent pixels' box when saving an image with no alpha channel, as the png plugin does. The option has no effect without alpha. Thanks. I've applied your patch to both branches. We prefer patches to go to bugzilla though, simply because they might be forgotten otherwise. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] New feature inquiry.
On Sun, 11 Jul 2004 13:46:09 -0400, Fredrik Alstromer [EMAIL PROTECTED] wrote: Hi all! The idea has been inspired by photoshop's effect layers, and the basic concept would be plugins that registers a new layer type. When sampled, the plugin is more or less simply executed, and the results are cached until any layer below the programmable layer has been modified. Layer modes and opacity are applied as if it was a normal layer, along with any layer mask. You actually want even more,. you want to be able to group layers and apply an effect to the group, instead of all layers below. An extensive example with an upside down layer list (should actually be flippable by just using a proxying GtkTreeModel), where the entire image contents is generated using procedural plugins and effects is at: http://freedesktop.org/~pippin/aluminium/screenshots/bauxite/2004-06-20b.png At the moment the application where this happens is a testbed, but it seems like design decisions done there about how to apply GEGL to an advanced layer stack seem sane. In it's current incarnation that implementation is disassembling the current layers into it's more atomic parts,. making the opacity of a layer an effect layer in itself, creating layers consisting of multiple atomic effects, is not a problem in this model and would allow creating a ui that in basic usage is equvialent, (or preferabbly more equvialent) to the current layers and channels dialog. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] color management
I haven't read the whole thread, but the last mail in the thread by William Skaggs seems very similar to the ideas discussed at gimpcon, what follows is my own understanding of what we discussed there: assuming working space of gimp == sRGB new image parasite_set (export_profile, sRGB) loading of file profile==sRGB best scenario, just load the file parasite_set (export_profile,sRGB) loading of file !profile no color profile associated with image convert from [sRGB (dropdown)] save as [sRGB (dropdown)] parasite_set (export_profile, users_choice) loading of file profile!=sRGB image has a color profile attached convert from [YUV (dropdown)] save as [sRGB (dropdown)] parasite_set (export_profile, users_choice) displaying the image while working on it this is actually the hardest thing to get right,. since it requires user interaction and cooperation,. even with a correct icc profile for the display the user can introduce errors to the display by fiddling with the brightness/contrast knobs. saving when export_profile == sRGB attach profile if possible saving when export_profile != sRGB this is of course dependent upon the file supporting the intended format, if it does pixel data should be converted upon saving, and the correct profile attached. /pippin ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Gimp 2.0.2 and elusive detachable tear-able menus
Gimp 2.0.2 and elusive detachable tear able menus Has anyone else experiences this? I can't get it to work. Say I bring the popup menu from the image, Layers, and press the dotted line. The menu detaches, but the moment the mouse leaves it it disappears. It re-shows when I switch to another desktop, but disappears the moment i try to place the mouse on it. I have no idea if this is a gtk problem, kde, or gimp?? $gimp --version GIMP version 2.0.2 $pkg-config --modversion gtk+-2.0 2.4.0 KDE 3.0.3-8 (stock from RH 8) $uname -a : Linux yoda 2.4.20-30.8.legacy #1 Fri Feb 20 18:58:10 PST 2004 i686 athlon i386 GNU/Linux Thanks, Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] color management
Hi, Øyvind Kolås [EMAIL PROTECTED] writes: new image parasite_set (export_profile, sRGB) loading of file profile==sRGB best scenario, just load the file parasite_set (export_profile,sRGB) loading of file !profile no color profile associated with image convert from [sRGB (dropdown)] save as [sRGB (dropdown)] parasite_set (export_profile, users_choice) This means that we would need to open a dialog for almost every image file the user opens. Is that a good idea? Shouldn't we just assume sRGB in that case? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] color management
On 12 Jul 2004 21:47:21 +0200, Sven Neumann [EMAIL PROTECTED] wrote: loading of file !profile no color profile associated with image convert from [sRGB (dropdown)] save as [sRGB (dropdown)] parasite_set (export_profile, users_choice) This means that we would need to open a dialog for almost every image file the user opens. Is that a good idea? Shouldn't we just assume sRGB in that case? We should provide a checkbox in the dialog, asking that the dialog newer be shown again, (it whould hide that part of the dialog, and a preference would be used to toggle it back on). /pippin ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 2.0.2 and elusive detachable tear-ablemenus
Please, by all means, update GTK+. Lots of bugs have been fixed in the 2.4 series and still using 2.4.0 is sortof lightheaded. Life is sort of slow with a 56K modem. Updated gtk+, glib and atk. The problem remains $pkg-config --modversion gtk+-2.0 2.4.4 $pkg-config --modversion glib-2.0 2.4.4 I guess that if no one else has this problem, it is a kde problem. I know there is a kde-3.0.5 available for RH 8.0, but I doubt something as obscure has been fixed in such a small upgrade. -Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 2.0.2 and elusive detachable tear-ablemenus
I guess that if no one else has this problem, it is a kde problem. That would also be my guess. I've been using Gimp with KDE 3.[012] for some time, and although I (contrary to you) never ran into anything that I knew should work but didn't, there surely were moments that made me doubt the cleverness of its focus policy. Gnome 2.6.(2, currently) works better for me with regards to that, so I recommend that you give it a shot (if possible) and see if the problem remains, to narrow down the range of imagined possibilities. Markus. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
