Re: proposal for managing resources such as brushes, gradients, etc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

chiming in here (getting back to speed).

There are some traits that make Bill's idea obsolete. First one
is the hierarchical organisation of resources. A tagging system
allows multiple ways to find a resource again (instead of a unique
one) by attaching many different properties to it (a single brush
can be: small, ragged, subtle, project XYZ, project ABC, old skool).
And this can only encourage reuse of a resource.

see: <http://www.mmiworks.net/eng/publications/2007/05/lgm-top-gimp- 
user-requests.html> topic 6. organise brushes, palettes, gradients in  
categories.

Also, having to 'tank' the resources in and out of the "workspace" is
a  waste of time, especially if you do 5 or more different graphics
jobs in a single day. Architecturally it feels a thousand times better
to have 'zero-conf': all the resources (say brushes) are 'just there',
and click a few tags (that match your needs) to narrow that down to
the dozen or so to start working.

Also the mentioning of both the file system and the preferences
(aka. the graveyard of any good idea) makes that a couple of
alarm bells go off here. There is no need for that.

William Skaggs wrote:

> Here is the idea:
>
> 1) You have a "workspace", holding the brushes that you are currently
>    interested in using.  The brushes shown in Gimp's brush picker are
>    those that belong to the workspace.  The user has complete control
>    over the contents of the workspace -- anything in it can be edited
>    or deleted.  The workspace is saved from session to session, and
>    automatically loaded at startup.
>
> 2) You have a set of extra folders, specified in Preferences.  The
>    brushes in these folders don't automatically belong to the
>    workspace.  To get at them, you invoke a Brush Chooser, which pops
>    up showing a list of brush folders, and a view, which can be either
>    a list or a grid.  Clicking on a folder causes the contents to be
>    displayed in the view.  Double-clicking on a brush in the view
>    causes it to be loaded into the workspace.  Once a brush has been
>    loaded into the workspace, it stays there until you delete it.
>
> 3) You can also use the Chooser to save a brush from the workspace
>    into the currently selected folder, assuming you have write
>    permission there.


     --ps

         founder + principal interaction architect
             man + machine interface works

         http://mmiworks.net/blog : on interaction architecture



_______________________________________________
Gimp-developer mailing list
Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux