Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
intertwingle [2008-11-15 17:40] – 81.188.78.24 | intertwingle [2008-11-15 17:56] – 81.188.78.24 | ||
---|---|---|---|
Line 25: | Line 25: | ||
* future. | * future. | ||
- | ===introduction.=== | + | ====introduction.==== |
Intertwingle can be seen as a unification of a search tool and an address book. It is not, however, a mail reader. The presentation of query results could be done through a mail reader, but the intention is that ones choice of mail reader should be orthogonal to the use of this tool. The two kinds of tools just happen to operate on the same data. | Intertwingle can be seen as a unification of a search tool and an address book. It is not, however, a mail reader. The presentation of query results could be done through a mail reader, but the intention is that ones choice of mail reader should be orthogonal to the use of this tool. The two kinds of tools just happen to operate on the same data. | ||
Line 217: | Line 217: | ||
There are objects, sets of objects, and presentation tools. There is a presentation tool for each kind of object; and one for each kind of object set. | There are objects, sets of objects, and presentation tools. There is a presentation tool for each kind of object; and one for each kind of object set. | ||
- | =====names, addresses, or people.===== | + | ====names, addresses, or people.==== |
The presentation tools for these kinds of objects needn' | The presentation tools for these kinds of objects needn' | ||
Line 231: | Line 231: | ||
The problem with the annotation notion is that it's the first time that we consider a piece of data which is not merely a projection of data already present in the message store: it is out-of-band data that needs to be stored somewhere. In the address book? In LDAP? I have no idea. | The problem with the annotation notion is that it's the first time that we consider a piece of data which is not merely a projection of data already present in the message store: it is out-of-band data that needs to be stored somewhere. In the address book? In LDAP? I have no idea. | ||
- | =====sets of people.===== | + | ====sets of people.==== |
Perhaps a simple list is sufficient, with options to sort in various ways (by last name, first name, email, host-name, or host-domain.) | Perhaps a simple list is sufficient, with options to sort in various ways (by last name, first name, email, host-name, or host-domain.) | ||
- | =====messages.===== | + | ====messages.==== |
Presenting a single message is straightforward: | Presenting a single message is straightforward: | ||
Line 241: | Line 241: | ||
Annotations of messages would be interesting as well. For example, one might want to make a note to one's self that two messages from different people refer to the same issue and should be dealt with at the same time. | Annotations of messages would be interesting as well. For example, one might want to make a note to one's self that two messages from different people refer to the same issue and should be dealt with at the same time. | ||
- | =====sets of messages.===== | + | ====sets of messages.==== |
This presentation has to be fairly powerful; it needs to present a decent summary of the messages (with resizable columns for sender, recipient, date, and so on) and be able to do all the usual sorting and threading tricks. Basically, this has to be a very good thread display. | This presentation has to be fairly powerful; it needs to present a decent summary of the messages (with resizable columns for sender, recipient, date, and so on) and be able to do all the usual sorting and threading tricks. Basically, this has to be a very good thread display. |