Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Tobias Jakobs
On Jan 18, 2008 8:55 AM, Sven Neumann [EMAIL PROTECTED] wrote:

 My current favorite approach is to put the tags into files in the
 ~/.gimp-2.x directory, one file per resource type. So there would be a
 brushrc, gradientrc, patternrc and so on. These files will contain
 metadata from the actual resource files.

One think I'm missing here is a way to share brushes with tags.
The user scenarios I'm thinking about is:
- Download package (ZIP-File) with a lot of brushes
- Install them (btw. Finding the right folder and copying them into it
looks like a problem for some users. At least it's an FAQ in the
German gimpforum.de.)
- Now I'd like to have this brushes tagged in Gimp and start working
with this brushes and I don't want to tag them myself.

Regards,
Tobias
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Chris Mohler
On Jan 18, 2008 5:03 AM, Tobias Jakobs [EMAIL PROTECTED] wrote:
 On Jan 18, 2008 8:55 AM, Sven Neumann [EMAIL PROTECTED] wrote:
 
  My current favorite approach is to put the tags into files in the
  ~/.gimp-2.x directory, one file per resource type. So there would be a
  brushrc, gradientrc, patternrc and so on. These files will contain
  metadata from the actual resource files.

 One think I'm missing here is a way to share brushes with tags.
 The user scenarios I'm thinking about is:
 - Download package (ZIP-File) with a lot of brushes
 - Install them (btw. Finding the right folder and copying them into it
 looks like a problem for some users. At least it's an FAQ in the
 German gimpforum.de.)
 - Now I'd like to have this brushes tagged in Gimp and start working
 with this brushes and I don't want to tag them myself.

What about a function to export brushes that dumps selected brushes
to a new dir with a local version of brushrc, and a matching import
that reads them in - file, MD5, and tags?

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


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread David Gowers
On Jan 18, 2008 9:33 PM, Tobias Jakobs [EMAIL PROTECTED] wrote:
 On Jan 18, 2008 8:55 AM, Sven Neumann [EMAIL PROTECTED] wrote:
 
  My current favorite approach is to put the tags into files in the
  ~/.gimp-2.x directory, one file per resource type. So there would be a
  brushrc, gradientrc, patternrc and so on. These files will contain
  metadata from the actual resource files.

 One think I'm missing here is a way to share brushes with tags.
 The user scenarios I'm thinking about is:
 - Download package (ZIP-File) with a lot of brushes
 - Install them (btw. Finding the right folder and copying them into it
 looks like a problem for some users. At least it's an FAQ in the
 German gimpforum.de.)
 - Now I'd like to have this brushes tagged in Gimp and start working
 with this brushes and I don't want to tag them myself.

 Regards,
 Tobias


An archive as follows:

brushrc/aqua
brushrc/charcoal
brushes/aqua
brushes/charcoal

,if extracted in your .gimp-2.4/ directory, should do the right thing.
Provided that brushrc filename references are either relative or have
no path component -- another implementation detail to work out.
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Sven Neumann
Hi,

On Fri, 2008-01-18 at 12:03 +0100, Tobias Jakobs wrote:
 On Jan 18, 2008 8:55 AM, Sven Neumann [EMAIL PROTECTED] wrote:
 
  My current favorite approach is to put the tags into files in the
  ~/.gimp-2.x directory, one file per resource type. So there would be a
  brushrc, gradientrc, patternrc and so on. These files will contain
  metadata from the actual resource files.
 
 One think I'm missing here is a way to share brushes with tags.
 The user scenarios I'm thinking about is:
 - Download package (ZIP-File) with a lot of brushes
 - Install them (btw. Finding the right folder and copying them into it
 looks like a problem for some users. At least it's an FAQ in the
 German gimpforum.de.)
 - Now I'd like to have this brushes tagged in Gimp and start working
 with this brushes and I don't want to tag them myself.

You are right that installing resources is a problem for most users. At
some point we should deal with this by adding functionality to import
resources files into GIMP. Ideally it should be as simple as dropping
the archive file or a folder on the Brushes list. GIMP should then ask
the user if the files should be copied into the main brushes folder or
if the folder location should be added to the brush search path. At the
same time GIMP could ask for tags to assign to the new brushes. Ideally
it would also look for a tags file in the folder and offer the tags
found therein as the default.


Sven


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


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Aurimas Juška
On Jan 18, 2008 9:55 AM, Sven Neumann [EMAIL PROTECTED] wrote:
 My current favorite approach is to put the tags into files in the
 ~/.gimp-2.x directory, one file per resource type. So there would be a
 brushrc, gradientrc, patternrc and so on. These files will contain
 metadata from the actual resource files.

What data structure could be used to represent this data in
application? As I understand, it will be necessary not only to
traverse data, but also to update it at runtime (not files, but
internal data structures, of course). Wouldn't it be nice to use
Sqllite for this instead?

 The only drawback is that if you remove files, their tags will be
 kept around forever.

They could be discarded after some period, say 90 days. Tags won't
make sense forever (because you'll forget why you added them), so
there is no point to keep them forever.
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Joao S. O. Bueno
On Friday 18 January 2008 15:08, William Skaggs wrote:
 In any case, let me ask a basic sort of question about user
 interaction.  Suppose I'm a user, painting with a set of brushes.
 I decide that I want to use a certain grunge brush.  (Let's
 say I have a specific brush in mind, but all I remember about
 its tags is that it is  a grunge brush from a set I imported last
 week.)  What are the steps I have to take, as a user, in order
 to find the new brush and start using it, without losing access
 to the other brushes I am currently using?  (I'm willing to assume
 that if I load everything with the grunge tag, I will be able
 to find the brush I want in there.)


Of couse, this will have to be refined by the UI team.
But I have two ideas for it: one would be abel to type in tags into a 
dialgo shwing brushes without lossing the ones already selected. 
Like, just typing more tags on the tag text entry widget, and having 
tehn combiend as or. The other one, is to allow the user to pop up 
another brushes dialog, in which he perfomes hs searches, He then can 
either select brushes from this ne dialog, or drag brushes from there 
to the first one, where they are transparently added to the group tag 
in use on the first window.

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


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread William Skaggs

I guess the reason I'm in such a fog is that all of the tag-using
systems I know about are cumbersome, and allow methods
other than tags to be used to help.  Google, for example, is
in some sense a tag-based navigation system -- and it's
great, but you wouldn't want to depend entirely on it for
your web navigation -- you also need bookmarks, history,
and the URL entry to get a usable system.  Bugzilla also uses
tags, but only as a component.  If it were possible to point to
a program that already implements the sort of thing you
have in mind, it would be very helpful to me.

In any case, let me ask a basic sort of question about user
interaction.  Suppose I'm a user, painting with a set of brushes.
I decide that I want to use a certain grunge brush.  (Let's
say I have a specific brush in mind, but all I remember about
its tags is that it is  a grunge brush from a set I imported last
week.)  What are the steps I have to take, as a user, in order
to find the new brush and start using it, without losing access
to the other brushes I am currently using?  (I'm willing to assume
that if I load everything with the grunge tag, I will be able
to find the brush I want in there.)

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


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread GSR - FR
Hi,
[EMAIL PROTECTED] (2008-01-18 at 0844.05 -0600):
 What about a function to export brushes that dumps selected brushes
 to a new dir with a local version of brushrc, and a matching import
 that reads them in - file, MD5, and tags?

Or a tag system based in companion files (flowers.gih gets a
flowers.gih.tags file) and then the common resource file is assembled
as need in similar fashion than .fonts.cache-1 (with any extra info it
can need, not just tags). No export tools need, no hidden info.

Provided tags files are simple enough (say one tag per line, which can
support languages or special types like tag assigned by user vs by
creator via simple syntax like type[lang]=tag), they could even be
merged with simple tools (concate the file, filter out duplicates) or
processed by script (create zip with all resources tagged flower).

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


[Gimp-developer] resource repository (thread renamed)

2008-01-18 Thread William Skaggs

From: Devin Watson [EMAIL PROTECTED]

 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. [...]

This sort of got sidetracked by all the traffic.  I'm not sure whether
there is a need for a new plugin registry, since Ingo has recently
set up a new one himself, but there seems to be still a strong
need for a web repository for other resources.  There was an
SOC project to create such a thing a couple of years ago, but
it did not ever get beyond a specification.

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


Re: [Gimp-developer] tagged resources such as brushes, gradients, etc

2008-01-18 Thread Sven Neumann
Hi,

On Fri, 2008-01-18 at 20:11 +0200, Aurimas Juška wrote:

 What data structure could be used to represent this data in
 application? As I understand, it will be necessary not only to
 traverse data, but also to update it at runtime (not files, but
 internal data structures, of course). Wouldn't it be nice to use
 Sqllite for this instead?

IMO a database would be overkill. This can easily be implemented on top
of GimpData and GimpContainer. I already added the GimpTagged interface
to GimpData yesterday. If it turns out that there's a performance
problem, GLib has the data structures we need to solve them.


Sven


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