#21
|
|||
|
|||
I guess I was thinking of the web as a point of comparison. While the web could certainly work if browsers simply showed a list of related/child pages in a separate pane, I think that would be less useful than the way it currently works; i.e., hyperlinks within the content.
I'm still not convinced that it has to be an either/or proposition. Granted, functionality should not become so fractured as to compete against itself, which is what I am understanding your objection to be. Perhaps it is counter-productive to mix metaphors, but I always imagined the ideal information manager would allow multiple "overlays" on top of a common data store. For instance, viewing data as a chronology, a hierarchy, a network (web), a list, etc. as shifting needs dictate. I confess I am less interested in strict representations or structures of information than I am in immediate context-sensitive usefulness. Strict schemas do not seem to work that well for shifting, ephemeral data like ideas, brainstorming, etc. For tasks, technical knowledgebases, etc., more rigid structure is of greater benefit. I guess I'd like to meet both needs at once. Quote:
|
|
|