Scott, I thought you came to the conclusion that there was no use for ordered tags. What changed your mind? Was it the abilty to browse hierarchical systems with the Journal? I also thought you came to the conclusion that turning directory names as tags alone worked. How would the results be different if you searched for:
a/b a b b a ? I imagine it's your idea of having the journal be able to browse hierarchically external devices, and the current filesystem above /home/olpc/Journal ? I love your idea of showing tags along side the journal entries. Clicking them would add them to the current search. Of course, there would be a limit to how many are shown for space-sake. As to Ivin's point that he brought this ui design to pentagram in the past, and it was rejected for being too complicated, I don't understand why they thought that. Having meta-tags (a tag which collects various tags, akin to dynamic virtual folders) and tags visible on the left would make: The most popular tags visible Tagging could be done by dnd object entries to the left-sided tags Clicking on the tags would add them to the search This seems like an easier taggin Journal to use, since tag management isn't "hidden" on the detailed view only. And if need be, the left tags pane could be toggled on/off by some 'tag' button. I hope Eben takes a look at your ui proposal and give it his Sugar love and polish to it :) Eduardo Eduardo 2008/9/23 Benjamin M. Schwartz <[EMAIL PROTECTED]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > C. Scott Ananian wrote: > | On Tue, Sep 23, 2008 at 2:13 PM, Benjamin M. Schwartz > | <[EMAIL PROTECTED]> wrote: > |> -----BEGIN PGP SIGNED MESSAGE----- > |> Hash: SHA1 > |> > |> C. Scott Ananian wrote: > |> | A hand-drawn proposal for what a Journal supporting "directory > |> | traversal" as well as tag space exploration is in the attached PDF. > |> | Discussion welcome! > |> > |> Could you please point me to a description of the semantics for these > |> "ordered tags"? Since I do not know how the tags are meant to work, I > |> cannot provide any feedback on the UI. > | > | Previous discussion: > | http://lists.laptop.org/pipermail/sugar/2008-September/008432.html > | > | Briefly: in addition to specifying multiple tags as "a b c" you can > | also separate some of the tags with slashes, like "a/b c". A search > | for "a/b" only turns up entries tagged "a/b" not entries tagged "b/a" > | or "a b", although a search for "a b" turns up all of them. > > OK, so if I understand you correctly, you are not actually adding any > semantics at all to the tags. What you are saying is that I can tag > objects with arbitrary strings that may include the "/" character, and > then filter objects by substring search on their tags. > > - --Ben > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkjZWOsACgkQUJT6e6HFtqRBpgCfd+Gxdi1Jfmam1++tTZLtyiBP > d60AniDjqESTQAMD3H+2/TYHYl36teI1 > =WI64 > -----END PGP SIGNATURE----- > _______________________________________________ > Sugar mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/sugar > _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
