Fwd: [Gimp-developer] Selection to brush/pattern/whatever in menus...
Please forgive me forwarded wrong message(carol's) by mistake previously. -- Forwarded message -- From: miriam clinton (iriXx) <[EMAIL PROTECTED]> Date: Sat, 13 Nov 2004 11:48:27 -0800 Subject: Re: [Gimp-developer] Selection to brush/pattern/whatever in menus... To: Laxminarayan Kamath <[EMAIL PROTECTED]> Laxminarayan Kamath wrote: >some day, someone write: > > >>I would say it would take me at least double or triple time to produce a >>website in GIMP comparable to the industry-standard websites I produce >>using a combination of Fireworks/Photoshop/Dreamweaver. >> >> >> >y do u use GIMP alone? just add it 2 ur long(?) list of apps. > > > Firstly - did you mean to reply to the group or just me? if the group, feel free to repost my message. its Free (licensed) anyhow ;) i don't just use GIMP... this is the end of a long thread... i'm a professional designer and have been forced in the past to use proprietary apps to get the effects i want, to be industry compliant and to simply find a user interface that is intuitive for a designer (who thinks in pictures) to use. i'm here on the invitation of RMS to try and comment from a designer's point of view on what may be missing or why designers find it impossible to get their heads around certain aspects of GIMP. gimp2 is very close but things like finding drop-shadow (an absolute essential, which really should be on the nav boards at all times) in Script-fu will put off a designer. designers dont like the word Script - they're scared of it. as for Script-fu, they'd have no idea... and Drop Shadow is hidden somewhere down the bottom. Even under Layer effects would be an idea - now thats not a bad one... very, very accessible and obvious. but the purpose of this thread is to do exactly this - its now being considered to implement such things under brushes i believe (i've been off for about a week so i'm still catching up). Gonna grab the bleeding edge CVS today - whats the latest stable-ish edition to compile and use on Mandrake 10.0 ? thanx mC~ -- 99% of aliens prefer Earth --Eminem www.iriXx.org www.copyleftmedia.org.uk -- Laxminarayan Kamath Ammembal MithraKoota, Bhoja Rao Lane, Mangalore 575003 (+91) 9845 061385 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.geocities.com/kamathln ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Fwd: [Gimp-developer] Selection to brush/pattern/whatever in menus...
-- Forwarded message -- From: Carol Spears <[EMAIL PROTECTED]> Date: Sun, 14 Nov 2004 09:44:14 -0800 Subject: Re: [Gimp-developer] Selection to brush/pattern/whatever in menus... To: "miriam clinton (iriXx)" <[EMAIL PROTECTED]>, GIMPDev <[EMAIL PROTECTED]> On Fri, Nov 12, 2004 at 02:41:41PM -0800, miriam clinton (iriXx) wrote: > Carol Spears wrote: hi, i am really glad that you stuck with this list. since making this excellent decision, might i direct you to this document: http://www.gimp.org/mail_lists.html and ask that you at least strip the mail the way they ask. they ask me to improve my hardware to work with them, but there are or could be people who are reading this list who store the mails or what have you where size is important. > >you took classes on how to use this software? or self-educated? > > > Oh and yes, for the record, I picked these tools up and used them - my > mother was a painter, not a graphic designer. I learnt the tools in > about 30mins. > > Compared to the GIMP which I still havent got my head around hence > my wanting to contribute - better to contribute than to whinge! > this is very nice. i dont think that it answered my question though. very nice to be raised in a loving environment with access to many tools and such. gimp was developed by people of all sorts. some had this sort of upbringing and access and some didnt. congratulations to you for deserving all this or whatever. my question, and i could have been more specific, was more about the software you use and the computer you use it on. classes in adobe/macromedia and experience with preinstalled operating systems is what i was looking for exactly. software will never be simple enough for people who need formal training in it. operating systems are difficult to install. i hear complaints from anyone who needs to install any operating system. i really am trying to determine if this is the case with you. if you are used to macintosh, there is a chance that you are used to having everything installed for you and TheGIMP and its fellow free apps might always be out of your grasp. none of this is personal. access is a nice thing. not having access and being able to get this stuff free and legal like is another thing. both are blessings or gifts from life? direct questions: did you have classes in using the software you are comfortable with? pay for books or tutoring? have you even been able to install an operating system on a computer you are in charge of? thanks, carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- Laxminarayan Kamath Ammembal MithraKoota, Bhoja Rao Lane, Mangalore 575003 (+91) 9845 061385 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.geocities.com/kamathln ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Fwd: [Gimp-developer] Selection to brush/pattern/whatever in menus...
-- Forwarded message -- From: Laxminarayan Kamath <[EMAIL PROTECTED]> Date: Sat, 13 Nov 2004 12:23:11 +0530 Subject: Re: [Gimp-developer] Selection to brush/pattern/whatever in menus... To: [EMAIL PROTECTED] some day, someone write: > > I would say it would take me at least double or triple time to produce a > website in GIMP comparable to the industry-standard websites I produce > using a combination of Fireworks/Photoshop/Dreamweaver. > y do u use GIMP alone? just add it 2 ur long(?) list of apps. -- Laxminarayan Kamath Ammembal [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.geocities.com/kamathln -- Laxminarayan Kamath Ammembal MithraKoota, Bhoja Rao Lane, Mangalore 575003 (+91) 9845 061385 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] www.geocities.com/kamathln ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Image reference count problem in plugin
I've got a plugin that attaches to an existing (displayed) image, and replaces it with a different image: gint newImage = gimp_file_load(...); gimp_displays_reconnect(oldImage, newImage); gimp_image_delete(oldImage); Problem is that (I think) the new image now has two references, so when the user closes the image display the image is not deleted. If that's right, is there any way to remove the extra reference? If not, what's going on? -- David Hodson -- this night wounds time ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
Hi, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: >>Sounds exactly like the plans we made at GimpCon 2000. > > Sorry I wasn't there. Perhaps you can meet in Hawaii sometime. That sounds like a lovely idea. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
>Sounds exactly like the plans we made at GimpCon 2000. > >Sven Sorry I wasn't there. Perhaps you can meet in Hawaii sometime. Juno Platinum $9.95. Juno SpeedBand $14.95. Sign up for Juno Today at http://www.juno.com! Look for special offers at Best Buy stores. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
Hi David, the onlything I still need is resizing/ rotating of patterns on the fly while I paint from the clone tool- or fill the images in. Any quotes ? :) - Cam David Neary wrote: Hi Cam, You sent this to me personally - would you mind sending it to the list? I think your ideas are pretty good, by the way. Also - are you interested in fleshing out properly the idea of bounties again? The response to your last request was poor, but I think that we could formalise something by working (with Sven) on a list of 5 or 10 bounties, and if we put a reasonable dollar figure with the features, and coordinate the bounty program with the release schedule, I think we can get a decent response. Cheers, Dave. Campbell J Barton wrote: To me this seams simple There are 2 different things- 1) Image Memory usage. (What it currently is) 2) Image Size (flat/expanded) - flat simply bing the memory used by the image assuming is was flattened expanded being the size of each layer added together - undo's etc Ignored. or even simpler 1) memory used by image 2) roughly the size of an umcompressed XCF 3) the size of the image as an uncompressed tiff/bmp whatever. An option for each would be nice :) - Cam David Neary wrote: Hi Joseph, Joseph Heled wrote: The caption below the image says 46.9 MB I add a layer with Layer/New Layer. The caption says 70.3 MB I delete the layer. Caption stays 70.3 MB I Layer/New Layer again. The caption says: 93.7 MB I delete the layer. Caption stays 93.7 MB Should I believe the numbers or not? I understand the gimp might be allocating memory and keeping it, but it does not mean the size of the image keep growing indefinitely? What am I missing? When you delete the layer, the delete step is registered in the undo stack. The undo stack is stored with the image in memory, so the layer actually moves from the layer stack to the undo stack. To change this behaviour, you could reduce the minimum number of undo steps saved to 1, say, which will discard the old data as soon as the undo stack goes past that number of steps (if you're making small changes like visibility changes, for example, your undo stack will grow much more, since the second undo parameter is the memory limit of the undo stack once you go past the minimum number of undo steps). Cheers, Dave. -- Campbell J Barton 133 Hope Street Geelong West, Victoria 3218 Australia URL:http://www.metavr.com e-mail: [EMAIL PROTECTED] phone: AU (03) 5229 0241 -- Campbell J Barton 133 Hope Street Geelong West, Victoria 3218 Australia URL:http://www.metavr.com e-mail: [EMAIL PROTECTED] phone: AU (03) 5229 0241 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] displaying gimp image sizes
I sent this directly do david by mistake To me this seams simple There are 2 different things- 1) Image Memory usage. (What it currently is) 2) Image Size (flat/expanded) - flat simply bing the memory used by the image assuming is was flattened expanded being the size of each layer added together - undo's etc Ignored. or even simpler 1) memory used by image 2) roughly the size of an umcompressed XCF 3) the size of the image as an uncompressed tiff/bmp whatever. An option for each would be nice :) - Cam -- Campbell J Barton 133 Hope Street Geelong West, Victoria 3218 Australia URL:http://www.metavr.com e-mail: [EMAIL PROTECTED] phone: AU (03) 5229 0241 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
Hi, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > Here's a thought - at some point, we expect that > there will be a recording mechanism for GIMP, and > when that happens, perhaps some coupling between it > and the undo mechanism would help reduce some > memory requirements for the undo mechanism. [snip] Sounds exactly like the plans we made at GimpCon 2000. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
Here's a thought - at some point, we expect that there will be a recording mechanism for GIMP, and when that happens, perhaps some coupling between it and the undo mechanism would help reduce some memory requirements for the undo mechanism. If we know whether a user action is deterministic, the undo action could rewind to a prior checkpoint where the image had been kept intact, and the actions since that time could be reapplied to advance up to the previous action. When a nondeterministic action occurs, a checkpoint mechanism would still need cause the image (or a portion of it) to be kept, but that would not be necessary for each step. Since creating a new layer is deterministic, deleting the layer should be able to be undone replaying the creation of the empty layer, thus, the undo action doesn't need to keep the empty layer in memory. Exceptions: Actions that take input from external sources would need to be treated like nondeterministic actions, causing a checkpoint to occur. Actions that use random numbers could record the random number seed that is used and be treated as deterministic. Just a thought... _-T Juno Platinum $9.95. Juno SpeedBand $14.95. Sign up for Juno Today at http://www.juno.com! Look for special offers at Best Buy stores. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] image growing size - is it true? is it normal?
Hi Joseph, Joseph Heled wrote: > The caption below the image says 46.9 MB > I add a layer with Layer/New Layer. The caption says 70.3 MB > I delete the layer. Caption stays 70.3 MB > I Layer/New Layer again. The caption says: 93.7 MB > I delete the layer. Caption stays 93.7 MB > > Should I believe the numbers or not? I understand the gimp might be > allocating memory and keeping it, but it does not mean the size of the > image keep growing indefinitely? What am I missing? When you delete the layer, the delete step is registered in the undo stack. The undo stack is stored with the image in memory, so the layer actually moves from the layer stack to the undo stack. To change this behaviour, you could reduce the minimum number of undo steps saved to 1, say, which will discard the old data as soon as the undo stack goes past that number of steps (if you're making small changes like visibility changes, for example, your undo stack will grow much more, since the second undo parameter is the memory limit of the undo stack once you go past the minimum number of undo steps). Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
