Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
intertwingle [2008-11-15 17:39] – 81.188.78.24 | intertwingle [2008-11-15 17:40] – 81.188.78.24 | ||
---|---|---|---|
Line 88: | Line 88: | ||
* Folders have names. | * Folders have names. | ||
* Folders are sometimes arranged in a hierarchy. | * Folders are sometimes arranged in a hierarchy. | ||
- | * Folders tend to store messages linearly, in a particular order: thus, each message has ``previous'' | + | * Folders tend to store messages linearly, in a particular order: thus, each message has "previous" |
* Messages can contain other messages (forwarded messages, or digests.) Each such message is a message in its own right, but the containment relationship can be important. | * Messages can contain other messages (forwarded messages, or digests.) Each such message is a message in its own right, but the containment relationship can be important. | ||
* Messages have bodies. | * Messages have bodies. | ||
Line 107: | Line 107: | ||
* All messages containing text in the main body, but not in an attachment. | * All messages containing text in the main body, but not in an attachment. | ||
* All messages with an attachment whose file name contains string. | * All messages with an attachment whose file name contains string. | ||
+ | |||
Line 152: | Line 153: | ||
</ | </ | ||
- | These objects are shallow: that last " | + | These objects are shallow: that last " |
Deeply nested MIME structures (multipart/ forms) are also flattened. Content-Disposition is always assumed to be inline for purposes of indexing; we index the body of any part that is of a text type. There is no special handling for multipart/ | Deeply nested MIME structures (multipart/ forms) are also flattened. Content-Disposition is always assumed to be inline for purposes of indexing; we index the body of any part that is of a text type. There is no special handling for multipart/ | ||
Line 210: | Line 211: | ||
All of the web search engines force the user to type in boolean expressions. Sometimes that's ok, but we should do something better, that lets the user construct expressions with a GUI. | All of the web search engines force the user to type in boolean expressions. Sometimes that's ok, but we should do something better, that lets the user construct expressions with a GUI. | ||
- | Drawing on the notion that searches are really set operations, perhaps one aspect of the search tool could be drag-and-drop: | + | Drawing on the notion that searches are really set operations, perhaps one aspect of the search tool could be drag-and-drop: |
==== 4. presentation tools.==== | ==== 4. presentation tools.==== | ||
Line 218: | Line 219: | ||
=====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' |
user = "Jamie Zawinski < | user = "Jamie Zawinski < | ||
Line 246: | Line 247: | ||
It should also be able to incrementally update as results are coming back from the database, so that the user can see the results they' | It should also be able to incrementally update as results are coming back from the database, so that the user can see the results they' | ||
- | Note that, to this view, the concept of ``folder'' | + | Note that, to this view, the concept of "folder" |
- | Today, I can point my ``message set browser'' | + | Today, I can point my "message set browser" |
- | Annotating a message-set could mean manually including and excluding specific messages: a message-set could be considered a ``bucket'' | + | Annotating a message-set could mean manually including and excluding specific messages: a message-set could be considered a "bucket" |
Presentation tools should be linked as well: one should be able to pick up the sets displayed in one tool and project them into another. For example: | Presentation tools should be linked as well: one should be able to pick up the sets displayed in one tool and project them into another. For example: | ||
* Show me all messages with word in body. | * Show me all messages with word in body. | ||
- | * Drag the sender column away: that's a set of people, therefore it is displayed using a ``people browser'' | + | * Drag the sender column away: that's a set of people, therefore it is displayed using a "people browser". |
* In the people browser, click on an address: refine the search to contain only those in the same domain as that address. A new, smaller list of people is presented. | * In the people browser, click on an address: refine the search to contain only those in the same domain as that address. A new, smaller list of people is presented. | ||
* Project the addresses of those people into a message-set-viewer: | * Project the addresses of those people into a message-set-viewer: | ||
Line 272: | Line 273: | ||
* show me a graph of the age-distribution of my unanswered mail, or, | * show me a graph of the age-distribution of my unanswered mail, or, | ||
- | * show me a graph of people who are known to have directly exchanged mail with each other so that I can see the ``clumping'' | + | * show me a graph of people who are known to have directly exchanged mail with each other so that I can see the "clumping" |
The object/ | The object/ |