[Gimp-developer] Fw: [Gimp-user] So it's a layer border - not a crop frame]
hi, there is an interesting discussion on the gimp-users list. i forward this because i am suggesting that the floating layer stuff be changed or even removed from this new gimp that has layers and such that work so well now for so long. - Forwarded message from John Dorfman [EMAIL PROTECTED] - one thing that i do not understand is the need for floating layers. i dont think that this term is being used properly here. is there any reason that there needs to be the extra step to make pasting directly to an existing layer easier? I don't think so. I believe there is (or was) a bug about that too. IMHO, when you paste, you should paste above the active layer, into a new layer, and be done with it. People can then move the layer merge down if they really want to, but as you say, once people discover layers they rarely anchor to the original layer directly. Hi, I'm new here and probably won't post often, but I think I have an answer to the origin of the floating layers. I was recently looking though the GIMP 1.3 manual. And if I remember correctly, it said something like this. There was a time in GIMP or some software that inspired GIMP where there were not layers. Thus for pasting, floating layers were born to crop and move, I believe, the pasted portion to the appropriate dimensions before anchoring. Hope this was what you were looking for! -John ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user - End forwarded message - could we rethink this and maybe get rid of the floating layer stuff? or at least make it so it is not the default behavior of a paste? carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Fw: [Gimp-user] So it's a layer border - not a crop frame]
Hi, Carol Spears [EMAIL PROTECTED] writes: hi, there is an interesting discussion on the gimp-users list. i forward this because i am suggesting that the floating layer stuff be changed or even removed from this new gimp that has layers and such that work so well now for so long. I don't think this needs any further discussion. I doubt that anyone would seriously disagree that floating selections should be removed or at least reduced. The point is that it needs an experienced GIMP hacker who wants to tackle this task. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Fw: [Gimp-user] So it's a layer border - not a crop frame]
On Tuesday 10 August 2004 05:53, Sven Neumann wrote: Hi, Carol Spears [EMAIL PROTECTED] writes: hi, there is an interesting discussion on the gimp-users list. i forward this because i am suggesting that the floating layer stuff be changed or even removed from this new gimp that has layers and such that work so well now for so long. I don't think this needs any further discussion. I doubt that anyone would seriously disagree that floating selections should be removed or at least reduced. The point is that it needs an experienced GIMP hacker who wants to tackle this task. Hmmm..Just for me to get a feeling on how it would work them: Instead of creating a floating selection, as it is now, a new full featured layer would come up. Maybe the anchor button could be preserved, in order to allow a quick merge with another layer of choice (either the previously used layer, from which the selection was copied or floated, or the next layer selected). I think this way all today's functionality would be preserved. Does the GIMP core treat these floating selections too different of actual layers? Or would a hack like placing a call to gimp_floating_sel_to_layer placed just after a floating selection get created do the job? (I am not suggesting that his should be the 'fix') Sven JS -- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Fw: [Gimp-user] So it's a layer border - nota crop frame]
Sven Neumann wrote: I don't think this needs any further discussion. I doubt that anyone would seriously disagree that floating selections should be removed or at least reduced. The point is that it needs an experienced GIMP hacker who wants to tackle this task. There is an almost trivial way of making floating selections disappear from the user's point of view: just cause any operation that creates a floating selection to automatically convert it to a new layer. The problem with this is that it would eliminate some very useful functionality: the ability to paste into a layer mask or selection mask (in QMask mode). Actually, it isn't obvious to me what even an experienced Gimp hacker could do to keep this functionality while removing floating selections. Best, -- Bill __ __ __ __ Sent via the KillerWebMail system at primate.ucdavis.edu ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Fw: [Gimp-user] So it's a layer border - nota crop frame
On Tue, Aug 10, 2004 at 07:49:53AM -0700, William Skaggs wrote: Sven Neumann wrote: I don't think this needs any further discussion. I doubt that anyone would seriously disagree that floating selections should be removed or at least reduced. The point is that it needs an experienced GIMP hacker who wants to tackle this task. There is an almost trivial way of making floating selections disappear from the user's point of view: just cause any operation that creates a floating selection to automatically convert it to a new layer. The problem with this is that it would eliminate some very useful functionality: the ability to paste into a layer mask or selection mask (in QMask mode). Actually, it isn't obvious to me what even an experienced Gimp hacker could do to keep this functionality while removing floating selections. leave Selection --Float there. make all other paste operations paste directly into a new layer. allow Floating Selections all the priveleges and cpu it historically has had. carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Article on GIMP in upcoming O'Reilly Windows Digital
Media Hacks book Reply-To: In-Reply-To: [EMAIL PROTECTED] Hi Joli, Joli Ballew wrote: I am Joli Ballew, coauthor of the upcoming O'Reilly book Windows Digital Media Hacks. I wrote a hack on GIMP, but my editor would like it to be beefed up a bit. It needs a hack angle, something that users won't readily recognize as something that's possible with the program, or something that's really unusual or off the wall. Well, what are you starting from? When you say you wrote a hack, do you mean something in script-fu, or perl-fu, or perhaps a C plug-in? I was hoping you could forward this email to someone at the company who can add the spice it needs to make it into the book. It shouldn't involve too much - the hack is written - it only needs the hack angle. Sorry - no company here. We're all volunteers. I'm forwarding your mail to the developers list, perhaps you can follow up with some more detail on what you've done so far. Cheers, Dave. -- David Neary, E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ Tél: 04 72 33 95 35 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] script-fu gimp-flip problems? procedural database execution failed
I'm trying to port a script from gimp 1.2 to gimp 2 everything else works fine except gimp-flip procedural database execution failed i tried searching for an answer but the only remotely similar thing suggested 'missing fonts' might be a problem gimp-flip works fine in the script CoolMetal. I cannot see what I'm doing differently, my script worked fine in gimp 1.2. gimp-flip is also in 3dTruchet but strangely commented out and didn't work for me when I uncommented it (and drawable is mispelt on the same line). (i think gimp-flip might have worked in truchet but i dont recall) Any ideas? - Alan PS it is inconvenient for me provide the script right now but I'll be submitting it soon anyway. (it is a rewrite of swirly-pattern.scm). ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu gimp-flip problems? procedural database execution failed
Alan Horkan ([EMAIL PROTECTED]) wrote: i tried searching for an answer but the only remotely similar thing suggested 'missing fonts' might be a problem gimp-flip works fine in the script CoolMetal. I cannot see what I'm doing differently, my script worked fine in gimp 1.2. gimp-flip is also in 3dTruchet but strangely commented out and didn't work for me when I uncommented it (and drawable is mispelt on the same line). gimp-flip in 3dTruchet has an image parameter while cool metal has not. Make sure that your script does not have an image parameter. Of course this is purely guessing, since you did not even provide the single line with the gimp-flip invocation... Hope this helps, Simon -- [EMAIL PROTECTED] http://simon.budig.de/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
