From: "Andy "Krazy" Glew" on
Skybuck Flying wrote:

> Let's call this new idea: "Tag" based file browsing ? ;)

It's not a new idea per se.

But it's a good idea.

And it's an idea that has not, AFAIK, been properly implmented in the filesystem.

I had some hope that Microsoft's WinFS might move in this direction, but

a) WinFS has been cancelled

b) rumor has it that WinFS was more structured than what you and I would like in this regard, Skybuck. Rumor has it
that WinFS had schema, and that files had to fit into particular schema. Overkill. Nice to have, but not nice to require.

---

I have been thinking about stuff like this (and occasionally posting) since before I left Canada. I think.

I remember Bill Joy talking at some office in Montreal, and talking about how it was silly that files might be named
/user/project or /project/user

e.g.

/project-p6/andy and /project-p6/john and /prject-wmt/andy and ...

The pathnames should be specifiable in any order.

Bill Joy said that Sun was working on this, and that it should soon come out.

Since I had been annoyed by stuff like this for years - yeah, sure, you can create symlink farms to do this, but that's
a pain - I was really excited.

I think this was while I was at McGill, before I left Canada In 1985.

But I'm still waiting.


From: "Andy "Krazy" Glew" on
Art Overby wrote:
>> Let's call this new idea: "Tag" based file browsing ? ;)
>>
>> Bye,
>> Skybuck :)
>
> http://code.google.com/p/tagfilesystem/

Cool.

I think there needs to be some thought on security. Filesystems are shared between users, not just private to a
security domain.


I think that it may be necessary to define points in the "pathname" above which tags cannot be reordered.



From: Aleksandar Kuktin on
> On Mon, 22 Feb 2010 08:56:01 +0100, Skybuck Flying wrote:

> [ ... ]
>
> Let's call this new idea: "Tag" based file browsing ? ;)
>
> Bye,
> Skybuck :)

But I like the filesystem. :(

Anyway, this can very well be implemented simply by creating a database.
So, you can designate a directory on your filesystem to serve this
purpose, you bring up a database program and point it in the right
direction. The database program will do all of your managing for you.

However, interfacing to this beast may be a chalenge..
In the most brutal way, the database program can be implemented as a
deamon which listens on a socket. And any and all programs which want to
access it can simply access the socket and start talking.

Then there is the problem of language (protocol).. And also of
integrating all that interface to user applications (which may be the
easiest part - load a special library and use it).

Hmm.. :/

I suppouse a localy runing gopher server as a front end to the said
database is a bit too elaborate? Plus, can gopher handle "uploads"?
From: "Andy "Krazy" Glew" on
Aleksandar Kuktin wrote:
>> On Mon, 22 Feb 2010 08:56:01 +0100, Skybuck Flying wrote:
>
>> [ ... ]
>>
>> Let's call this new idea: "Tag" based file browsing ? ;)
>
> But I like the filesystem. :(

At the very least such a tag based filesystem needs permalinks. Otherwise, the "path" (which is really a query) that
you type to obtain a file one day might return a group of files the next.

Of course, that can happen in filesystems to. A filename can be changed to a directory, and/or paths can be moved around.

I think that the concept of "folder" is pleasant. Drop a file in a folder whose path is /a/b
- i.e. who is tagged "a" and "b" - and the file automatically gets tagged "a" and "b".
From: Stephen Fuld on
On 2/21/2010 11:56 PM, Skybuck Flying wrote:
> Hello,
>
> Sometimes files/folder belong to different categories at the same, for
> example: "graphics related", "music related", "programming related", "math
> related".
>
> Currently windows requires me to put the file in folders, this creates a
> "static" view of the situation. In reality I like placing all the
> files/folder in one big folder so I can "easily" find everything.
>
> However when the number of files reaches thousands or ten thousands it
> becomes a bit harder to "sift" through it... I have no real way of
> "filtering out" unwanted files, or "filtering/zoom into the files I wanna
> see".
>
> So I recommend a new way of looking at files in the file system:
>
> The user receives the ability to "tag" files. Which means the user can now
> start adding "tags" to files.
>
> So for example:
> MyGameSource.cpp tags: "c++", "game development", "graphics", "game engine",
> whatever.
>
> Then the next time I want to "sift" through my files... for example I want
> to see all "graphics" related files...
>
> So then I type the "tag" search term into the windows explorer like so:
>
> Graphics
>
> The future windows/file explorer should filter out all other files which are
> not graphics related.
>
> Another example:
>
> tag: "redcode" ;)
>
> Search: "redcode"
>
> All files related to redcode are shown...
>
> This could be done for the current folder, there should also be an option
> which says: "Search subfolders as well" and display those results as well !
> ;)
>
> Let's call this new idea: "Tag" based file browsing ? ;)

Look at the Lifestreams system.

http://cs-www.cs.yale.edu/homes/freeman/lifestreams.html

I thin it does what you want. All of your documents are kept in one
chronological "file", which is called your lifestream. In addition,
there are tags/indexes that can be applied to each document that can be
used as a retrieval mechanism. Some are automatic, such as "graphics",
or "e-mail". But you can also define your own, such as "Project foo", or
"Wife", or whatever.


Newsgroups trimmed


--
- Stephen Fuld
(e-mail address disguised to prevent spam)