After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335332 - leaftag integration
leaftag integration
Status: RESOLVED WONTFIX
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-21 09:20 UTC by David Trowbridge
Modified: 2010-04-16 21:39 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
leaftag integration (11.17 KB, patch)
2006-03-21 09:21 UTC, David Trowbridge
none Details | Review
Updated Leaftag Integration Patch (11.19 KB, patch)
2006-10-25 21:32 UTC, Kevin Kubasik
needs-work Details | Review

Description David Trowbridge 2006-03-21 09:20:29 UTC
Here's a preliminary patch adding a tag dialog and column to nautilus, conditionally compiled in.  It works pretty well for me right now.  When/if leaftag gains an async API, I'll update it to use that.
Comment 1 David Trowbridge 2006-03-21 09:21:09 UTC
Created attachment 61675 [details] [review]
leaftag integration
Comment 2 Christian Neumair 2006-03-21 10:42:58 UTC
Thanks for your efforts, milestoning to Nautilus 2.16.
Comment 3 Alexander Larsson 2006-07-07 12:07:06 UTC
From a performance perspective this seems like a total non-starter. Not only does it do a blocking call which is forbidden in nautilus, it does (unless i'm misreading the code) a separate sql query for each file. So, reading a directory with 1000 files we'll be doing 1000 blocking sql queries...

At the minimum we need an asynch mechanism for this that can get all the tags for all the files in the directory in one go. Ideally it would also support change notification so that the UI can always be up to date.

Also, I'm not sure it makes sense to have a separate library and database just for tags. We really should use the same mechanism to store all dead metadata (i.e. icon positions, custom icons, emblems, notes, tags). Of course, such an implementation must also handle all the requirements we have: change notification, safe cross-process use (even on NFS $home), and it should not corrupt the db if accessed from two machines concurrently on shared NFS (its ok if we don't get a perfect user experience in this case, but we should not destroy data).

From a nautilus integration perspective I also think this needs more thinking, as it sort of conflicts with emblems. Emblems are essentially tags already, so just dumping in another form of tags next to it is looking kinda weird.
Comment 4 Kevin Kubasik 2006-10-25 21:32:00 UTC
Created attachment 75415 [details] [review]
Updated Leaftag Integration Patch

Just an update that I got to build and run, however, it has some major functionality issues, and crashes a lot. And is very slow. Maybe leaftag is overkill to some extent, but we need to come up with one centralized place to keep this metadata about files. Its find it nautilus wants to do it (assuming of course the emblem GUI gets a major overhaul at some point ;) ) but I think we need to get this somewhere.
Comment 5 Cosimo Cecchi 2008-04-05 14:04:05 UTC
Setting right patch status as for comment #3 and comment #4.
Comment 6 Cosimo Cecchi 2010-04-16 18:14:55 UTC
It looks like the project is not maintained anymore. Closing as WONTFIX.