Hi,
On Thu, 2008-01-17 at 20:52 +0200, Aurimas Juška wrote:
> I don't see any disaster. Here is one possible solution: store some> sort of checksum (let's say, MD5) together with filename in the> database.
MD5 checksums are a nice idea. I think I will incorporate that for theimplementation of tagged resources.
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 abrushrc, gradientrc, patternrc and so on. These files will containmetadata from the actual resource files. At some point they will haveenough metadata to actually skip loading the resource file until it isactually used. That way we can avoid the need to load all resource filesat startup.
As a first step the implementation will concentrate on tags. So for nowall that goes into the file per resource is
- filename, either absolute or relative to ${gimp_dir} - MD5 sum for recovery - list of tags
If a resource file with tags is lost (i.e. it doesn't exist under thefilename any longer), the filename will be removed but the MD5 sum andtags will be kept. When the user adds new resource files, their MD5 sumsare compared to the checksums of the entries without filename and tagsare recovered from there. This is not perfect, but it should work quitewell. The only drawback is that if you remove files, their tags will bekept around forever. But I guess we can live with that. The lost entriescan be kept at the bottom of the tags file so they can be easilydiscarded manually. At some point we might even add a user interface forthis.
Does this make sense or did I forget something important?
Sven
_______________________________________________Gimp-developer mailing listGimp-developer@xxxxxxxxxxxxxxxxxxxxxxxxxxx://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
