Tagging? In Nautilus? *explode*

Check this out (mpeg4, VMware video codec). Ahh yeah. David’s putting together some awesome code for tagging functionality in nautilus using Leaftag. Hopefully we’ll get it out into a release before long.

19 thoughts on “Tagging? In Nautilus? *explode*”

  1. That looks amazing. This is the first thing that I have seen that actually addresses the problem of collecting the information for these fancy searching programs to use.

    How does this stuff work with the existing emblems in nautilus?

  2. Please post your videos as ogg theora. We are never going to solve the codec/patent issue unless we actually start using the codecs.

  3. Until I have a tool that makes it as easy to convert to theora as mpeg4 (which in thise case required two seconds to copy some command line arguments from the enxamples section of the mencoder man page), it’s not going to happen. I have better ways to spend my time than digging through mountains of poor transcoder documentation trying to find the magic command line options to make it not look like crap.

  4. Now as long as the information is put somewhere in the extended attributes or put right into the metadata so that programs like f-spot, beagle and the like can access it.

  5. Corey: It’s up in MPEG-4 (for convenience) and VMware’s native video format (for efficiency). VMware’s format is basically VNC, and mplayer has an open source decoder for it. Unless you can find some patent issues in VNC, it’s probably clean. Theora is great and all, but it really isn’t what you want to be using for screen captures.

  6. Ugh.. I guess I should add that “theoretically” the vmware video format is more efficient. I have no idea why, even after gzip, it’s 1.8MB compared to the MPEG-4’s 400k. Are there actually any formats out there (besides Flash, or raw VNC dumps) that are good for screen capture data? Even if Theora gets similar performance to MPEG-4 on this stream, that really isn’t saying much.

  7. Thanks, it’s nice to read things are coming into shape, i’d like to add my note though:

    Leaftag has the potential to merge the “Emblems” and “Notes” features, already present in GNOME’s file properties dialog, into one single dialog. That would be preceived as a natural evolution, this is a big chance to simplify & improve the property dialog.

  8. Pingback: Fudeblog by Cesar Cardoso » Aqui e ali

  9. David Trowbridge

    In reality, this dialog and epiphany’s aren’t that different.

    Take a look at this: http://home.exetel.com.au/harvey/epiphany/bookmark/list2.png

    Both have a text entry, which is meant to be the “primary” mode of interaction. Both have a list of your existing tags. The difference is that leaftag will have bundles (like del.icio.us), and potentially hundreds of tags per user. As discussed with the previous fstaglib nautilus screenshot, the big list of check-boxes just doesn’t scale. It’s my hope that with bundles (imagine more expander boxes below “all tags”), this UI can elegantly handle that many.

  10. The most interesting thing is how the topics are used to construct the bookmarks menu. Also how the same algorithm defines the ordering of topics in our list.

    While the UI suggested for Nautilus does pack more tags into the screen, it might be worthwhile to try using Epiphany’s heuristic for automatically identifying topics the user will want to use. For example, “currently selected” tags at the top, “suggested/related” tags immediately beneath, and “all” tags below.

    Our animation isn’t as slick, but you can see roughly how the “suggested” tags work by watching this a few times:

  11. David Trowbridge

    After thinking about this, I’m a little reticent to have things “move around.” Unless it behaves perfectly (unlikely given the nature of humans), anything other than alphabetical order can make things unpredictable and difficult to find, especially in a list of hundreds of tags.

    I am, however, very interested in the “suggested/related” heuristic. Having another synthetic bundle at the front for suggestions would be very nice 🙂

  12. Seems that my ISP doesn’t like “potentially copyrighted forms of files”. I’ve placed it on my uni page instead.

    I agree that the idea of an auto-generated bundle would be nice, if you are really going to have a huge number of tags. We may even leverage that in Epiphany later, if users start having >100 topics. But this is Epiphany’s answer to bookmark hierarchies, and so ensuring it scales well to reasonably large topic/bookmark collections was important to us as well.

    By the way, why use space as a separator? You’re ruling out the user’s option to have space in their tag/topic names. You can’t write “Open Source” or “Jack’s Birthday” easily with space separators. Basically, I’m wondering why not use commas?

    Also note that Epiphany requires an explicit “Create New Topic”, though this is negotiable. We did it to ensure that users don’t accidentally write “Opne Source” and end up very confused. It was also easier to implement that way given our current codebase. 🙂

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top