On Jan 18, 2008 9:55 AM, Sven Neumann <sven@xxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
