Re: [Gimp-developer] An idea for resource management
It would be worthwhile to consider this kind of thing for gradients and palettes, too -- personally I find I often simply want a scratch area; and being required to create a new palette first is a bit troublesome, especially since I usually don't want it to be saved. I could write a plugin that clears a specific palette and then switches to it, that would be good, actual infrastructure in GIMP for scratching around would be better. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] An idea for resource management
On Mon, 2008-05-19 at 18:45 +0930, David Gowers wrote: [...] > I like this workflow. It makes me think of an idea, where you can have > 8 custom brushes attached to your image (and saved with it); when you > load the image, they appear in your brushes dialog [...] Some (proprietary) software has the ability to do similar things with fonts. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org www.advogato.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] An idea for resource management
Robert Krawitz wrote: >Date: Sun, 18 May 2008 18:55:07 -0400 >From: Brian Vanderburg II <[EMAIL PROTECTED]> > >I don't know if this has been talked about yet but could be nice for a >future version of GIMP. > >Currently, in order to use a custom brush/gradient/etc, you must first >create it, then edit/save/etc. Every time you want a new brush you have >to create a new one, even if it is a temporary brush. Instead why not >have the 'active' brush (and gradient,etc) always be user editable, >saved between sessions. > > How would you restore the original version of the brush, in case you > edited it accidentally? > > When you double-click on the brush in the brushes dialog (say Brush1), it would copy that brush's settings to the internal active brush. Changing the active brush would not change the settings of Brush1. To restore the original Brush1 settings, just double-click it again and it would copy Brush1 to the active brush again. To save settings you would just click the save button and type the name of the brush to save to, even Brush1 to overwrite it with new settings. The 'active' has all the settings of a brush, but it is a private brush (it has no name and is not shown in the brushes list). As you select a new brush in the brushes list it just makes a copy of that brush in memory to the active brush. The idea is there is a global active brush in memory, all painting is done with it (or if it is not saved between tools, then each tool has it's own active brush). Selecting a brush loads that brush and sets the settings on the tool's active brush. Even it the loaded brush is read-only, the active brush can be edited, and upon closing the program, would be saved out to a special location in the user data directory, not back to the brush it was loaded from. The user can choose to save the brush, in which case a text entry dialog would appear allowing the user to save. The same could be done with gradients, Loading a gradient simply loads the selected gradient into an active gradient, which can always be edited without being saved back out. Then tools that use a gradient use the active gradient. If the user changes to a different gradient it just loads that gradient into the active gradient. When closing it saves it in a special area somewhere. The user could save the gradient to a gradient file also. Just an idea. Brian Vanderburg II ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] An idea for resource management
On Mon, May 19, 2008 at 5:41 PM, Aurimas Juška <[EMAIL PROTECTED]> wrote: > Hi, > > On Mon, May 19, 2008 at 2:05 AM, Robert Krawitz <[EMAIL PROTECTED]> wrote: >> Currently, in order to use a custom brush/gradient/etc, you must first >> create it, then edit/save/etc. Every time you want a new brush you have >> to create a new one, even if it is a temporary brush. Instead why not >> have the 'active' brush (and gradient,etc) always be user editable, >> saved between sessions. >> >> How would you restore the original version of the brush, in case you >> edited it accidentally? > > How I understand the idea, the 'active brush' is a copy of the brush > that you've selected. So you can play with it in any way you like > without breaking the original brush (which could be a read-only file, > btw). > > Workflow could be something like the following: > 1. Select a brush. A copy of it is created transparently to the user. > 2. User can easily edit the brush for her needs. > 3. Paint something > 4. (optionally) Save the brush to disk. > 5. Select another brush. A copy of it is created transparently to the > user. Previous 'current brush' is lost. I like this workflow. It makes me think of an idea, where you can have 8 custom brushes attached to your image (and saved with it); when you load the image, they appear in your brushes dialog as 'myimage.xcf work brush #N', and are stored in a temporary location on disk.). When a non-custom brush is selected, it is copied to the oldest custom brush (which then becomes the newest, and is made active). Selecting between custom brushes affects which one is currently edited (and of course, being drawn with :) When the image is saved, the brushes are stored as well (from their temporary locations). ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] An idea for resource management
Hi, On Mon, May 19, 2008 at 2:05 AM, Robert Krawitz <[EMAIL PROTECTED]> wrote: > Currently, in order to use a custom brush/gradient/etc, you must first > create it, then edit/save/etc. Every time you want a new brush you have > to create a new one, even if it is a temporary brush. Instead why not > have the 'active' brush (and gradient,etc) always be user editable, > saved between sessions. > > How would you restore the original version of the brush, in case you > edited it accidentally? How I understand the idea, the 'active brush' is a copy of the brush that you've selected. So you can play with it in any way you like without breaking the original brush (which could be a read-only file, btw). Workflow could be something like the following: 1. Select a brush. A copy of it is created transparently to the user. 2. User can easily edit the brush for her needs. 3. Paint something 4. (optionally) Save the brush to disk. 5. Select another brush. A copy of it is created transparently to the user. Previous 'current brush' is lost. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] An idea for resource management
Date: Sun, 18 May 2008 18:55:07 -0400 From: Brian Vanderburg II <[EMAIL PROTECTED]> I don't know if this has been talked about yet but could be nice for a future version of GIMP. Currently, in order to use a custom brush/gradient/etc, you must first create it, then edit/save/etc. Every time you want a new brush you have to create a new one, even if it is a temporary brush. Instead why not have the 'active' brush (and gradient,etc) always be user editable, saved between sessions. How would you restore the original version of the brush, in case you edited it accidentally? -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gutenprint --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
