https://bugs.kde.org/show_bug.cgi?id=332665--- Comment #64 from Vishesh Handa <
[hidden email]> ---
(In reply to Veaceslav Munteanu from comment #63)
> Here are some answers to your questions, Jeff:
> 1. digiKam has options in settings menu to enable/disable read/write
> 2. If you change data from digikam and write is enabled, tags, ratings and
> comments are automatically syncronized
> 3. If you have read enabled, data from baloo is read when any read metadata
> operation is triggered
"data from xattr is read ..."
> 4. There is no way for digiKam to know if data was changed from outside. At
> least at this moment.
file system monitoring? inotify provides signals on when a file's attributes
have been changed. Or rather do a full scan on startup or when the user
requests it and check the ctime of the files?
> 5. If digikam has a tag structure like, aaa/bb/cc/dd, digikam store tags
> with KFileMetadata as "dd" without it's full path. We can store the full
> path, but tag itself will be unreadable in Dolphin. Also, because of read
> after write, we could end up with a lot of duplicate tags in digiKam tag
> tree. Thats why we store them under a special branch, which is now called
> "BalooTags" so it won't pollute the whole tag tree.
>
I've said this before, I really really disapprove of using the name
"BalooTags". If you must use something, use "Digikam". At least the user will
then know which application these tags come from. Adding the name Baloo gives
them nothing of value and in-fact would confuse them even know since I keep
telling everyone that Baloo no longer handles tags.
Maybe I should just submit a patch.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
