Re: [Gimp-developer] Script-Fu - Batch Mode Problem
On Thu, 2002-12-19 at 18:34, Patrick McFarland wrote: On 20-Dec-2002, Steinar H. Gunderson wrote: On Thu, Dec 19, 2002 at 11:29:08PM -, [EMAIL PROTECTED] wrote: That's what I thought as well...but the scaling with imagemagick was causing pixelation. Scaling up or down? With which filter? (You're sure you resampled and not did a simple quick rescale, right?) If your're scaling down in gimp, go into preferences, and change scaling mode to linear. Cubic sucks for scaling down, and Im not sure why Gimp even allows users to make a choice (bicubic and such are always used for scaling up, bilinear and such are always used for scaling down.) Do you even use gimp? When downsampling gimp will use bilinear filtering even when bicubic is specified. There are usefull techniques that require the use of nearest neighbor or bilinear resampling. I'm not sure why gimp would do a better job of downsampling than imagemagick. It doesnt do anything fancy, just a rectangular area-sample. -- Jay Cox [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: Re: alpha vs. transparency / translucency
Hi, Guillermo S. Romero / Familia Romero [EMAIL PROTECTED] writes: [EMAIL PROTECTED] (2002-12-19 at 1208.55 +0100): the user shouldn't be confronted with the term RGBA at all. IIRC, this is the case unless she's writing a script or plug-in in which case she is not a user any longer but a developer. Then no confrontation with CMYK either, or with bit depth or DPI or moire or lots of other terms. Sorry, but all these are terms of the trade, dunno why should that be not under user control and view, at least if the app is not a basic paint app but something more advanced I agree for CMYK, DPI as well as RGB, but I don't think that RGBA is a commonly used term and it should thus not be used in the user interface and AFAIK it isn't. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Script-Fu - Batch Mode Problem
Hi, [EMAIL PROTECTED] writes: I had posted this earlier to the gimp-users listSomeone suggested that I may find an answer on this list. I am looking for an suggestion you can provide. I am having an issue with a Script that I have written being called from the command line. we will only be able to help you if you provide the script or (preferably) a smaller test script that triggers the problem. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] List of changes for the future 1.2.4 release
Hi, Raphaël Quinet [EMAIL PROTECTED] writes: Note that just checking write() or fwrite() return values may not be enough: some filesystems delay the error indictation until close() is called on the fd. So this bug may well be influenced by the filesystem GIMP is writing to at the time. Yes, this is very important! Checking only the return value of fwrite() and ignoring the return value of close() is a recipe for disaster. You should also bear in mind that some filesystems (even the good old ext2) may behave differently if quotas are enabled. please reopen the bug-report then. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] New Gimp FAQ: Call for questions
On Thu, 19 Dec 2002, Michael J. Hammel wrote: Thus spoke David Necas (Yeti) IMHO novice mode (if ever implemented) should restrict the things user can do to some sane set (simplifying the interface), and not try to turn the Gimp into Eliza Most of the time that I've heard of problems like this it has been when the wrong layer has been selected or a layer with transparency is in use and the user doesn't understand why you can't draw in a transparent area. Novice mode might be as simple as forcing users to use a single layer that doesn't have transparency enabled by default, allowing them to learn the rest of the programs features without complicating their experience with layers. In my experience, it's most frequently been when some kind of select/cut/paste operation has created an un-anchored extra layer. In that case, the novice (who realises that layers are a complication - and is ignoring them for now) has the implications of layers forced upon them. Just a thought. I'm not convinced that a novice mode is worth it though, for all the same reasons mentioned already (like every novice will think something in novice mode is still to difficult to understand). I dislike the idea of novice mode too. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation Training (817)619-2466 (Fax) Work: [EMAIL PROTECTED] http://www.link.com Home: [EMAIL PROTECTED] http://www.sjbaker.org ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Re: Re: alpha vs. transparency / translucency
[EMAIL PROTECTED] (2002-12-20 at 1246.03 +0100): I agree for CMYK, DPI as well as RGB, but I don't think that RGBA is a commonly used term and it should thus not be used in the user interface and AFAIK it isn't. You should then check GIMP's Compose operation, you can compose three images as RGB, or four as RGBA. And when you inspect a PNG you can get ones that are RGB and some others that are RGBA (file(1) reports all this correctly), no coder voodoo, but plain user interests. For me and the people I know around, RGBA is a perfectly normal term, at the same level of the others. GSR ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] A Free Software project of interest.
I saw this program and thought it might be interesting to GIMP users and developers. http://www.vips.ecs.soton.ac.uk/ Hopefully Gimp 2.0/GEGL/PUPUS will use some of the ideas there. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] List of changes for the future 1.2.4 release
On 20 Dec 2002, Sven Neumann wrote: Hi, Raphaël Quinet [EMAIL PROTECTED] writes: Note that just checking write() or fwrite() return values may not be enough: some filesystems delay the error indictation until close() is called on the fd. So this bug may well be influenced by the filesystem GIMP is writing to at the time. Yes, this is very important! Checking only the return value of fwrite() and ignoring the return value of close() is a recipe for disaster. You should also bear in mind that some filesystems (even the good old ext2) may behave differently if quotas are enabled. please reopen the bug-report then. No need; we check fclose()'s return value in both branches now. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
