Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-17 Thread peter sikking
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

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-17 Thread Scott
On Thu, Jan 17, 2008 at 05:39:29PM +0100, peter sikking wrote: 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

Re: [Gimp-developer] proposal for managing resources such as brushes , gradients, etc

2008-01-17 Thread Scott
On Thu, Jan 17, 2008 at 08:37:34AM +0100, Sven Neumann wrote: And, to repeat, even if there is tags support, there must be, at least from the user's point of view, something like a workspace -- a set of brushes that are immediately available. Sure. That is the set of brushes that match

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-17 Thread Aurimas Juška
On Jan 17, 2008 7:45 PM, William Skaggs [EMAIL PROTECTED] wrote: 2) If they are stored in a separate database, keyed by file names, then there is a great danger of losing the linkage between tags and object. If, for example, the user renames the directory holding some brushes, all of the

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-16 Thread Alexia Death
At the level of programming, the only relatively difficult thing is to create the GimpDataChooser widget. Even this is simple in principle, although complicated in practice because it involves a lot of rather complex Gimp code. I have been experimenting with writing a Chooser, and I

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-16 Thread Sven Neumann
Hi, On Wed, 2008-01-16 at 17:03 +, William Skaggs wrote: This problem has been discussed several times in the past, and proposals have been made about how to address it. I have been thinking about it recently, and have come up with a somewhat different, and I believe simpler approach,

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-16 Thread William Skaggs
From: Sven Neumann [EMAIL PROTECTED] Right. We have discussed this in the past and we have come up with a simple and IMO very good solution that has several advantages over the approach that you are suggesting now. The solution is to allow tags to be assigned to data files. This allows the

Re: [Gimp-developer] proposal for managing resources such as brushes, gradients, etc

2008-01-16 Thread Sven Neumann
Hi, On Wed, 2008-01-16 at 20:42 +, William Skaggs wrote: This mixes together two separate issues. No, it doesn't. Absolutely not. Tags are, as I have already agreed, an excellent way of doing a search mechanism. They don't get rid of the need to have a workspace, though. Suppose I

Re: [Gimp-developer] proposal for managing resources such as brushes , gradients, etc

2008-01-16 Thread Devin Watson
I'm sorry to jump in on this so late. I was working on a new GIMP Plug-In Registry. It had been put on pause by me because of certain life-altering events. At one point I had put forward the idea of a backend XML-RPC or SOAP connectivity service that would allow GIMP to access the

Re: [Gimp-developer] proposal for managing resources such as brushes , gradients, etc

2008-01-16 Thread Sven Neumann
Hi, On Thu, 2008-01-17 at 01:50 +, William Skaggs wrote: These are interesting ideas, but they are fantasies at this point. The whole tags thing is a fantasy at this point. There is no infrastructure in Gimp to support it, so everything would have to be written from scratch. That's