Forum Posts Feed
EccoPro: Why has nobody developed a clone so far?
< Next Topic | Back to topic list | Previous Topic >
Pages: ‹ First < 2 3 4 5 6 7 8 9 10 > Last ›
Posted by David Dunham
Aug 30, 2007 at 04:22 AM
Stephen R. Diamond wrote:
>I _meant_ collapsing (the word had slipped my mind), although “folding” often (and
>perhaps in best usage) refers to yet a fifth way: by showing only the first line of an
>item.
That was #3 on my list. But thanks.
So is there a 5th way to hide info?
I seem to recall that Framework would show you what was on the *back* of a topic. (The data is in the front; I think some sort of script was on the back?)
I guess showing and hiding columns could be a way too, though it’s a stretch.
Posted by Alexander Deliyannis
Aug 30, 2007 at 07:04 PM
David Dunham wrote:
>So is there a 5th way to hide info?
>
>I seem to recall that Framework would show you what was on
>the *back* of a topic. (The data is in the front; I think some sort of script was on the back?)
One could say that metadata is a way to hide info. In UltraRecall, you can have the item ‘Details’ pane (i.e. document) taking most of the window space up front, and stack various tabs underneath it (or wherever), including Notes (which is an RTF document itself), and Attributes (metadata).
So the tree is just one way to organise the info. At the item level, you can organise additional info around it, without needing to see it all the time.
alx
Posted by Stephen R. Diamond
Aug 30, 2007 at 08:25 PM
David Dunham wrote:
>Stephen R. Diamond wrote:
>
>>I _meant_ collapsing (the word had slipped my mind),
>although “folding” often (and
>>perhaps in best usage) refers to yet a fifth way: by
>showing only the first line of an
>>item.
>
>That was #3 on my list. But thanks.
Yes, I see - Shriking. I think those four exhaust the means of hiding topics in a tree, but perhaps they are exhaustive for the trivial reason that “filtering” can subsume anything.
The question might actually be put as ‘What are the possible means of filtering headings in an outline.’ Included would be 1) the means available to specify filters; and 2) the default filter operations. 1) is more important in a database program and 2) in pure outliners. The default filter operations that have found recurrent use in outliners are; collapsing (if it can’t collapse, it isn’t an outliner); hoisting (focusing); and folding (shrinking). Additional default filter operations appearing in some publicly available software have included double hoist (two independent heading hoisted at the same time -ADM) and hoist on hoist (hoist relative to hoisted headings - NoteMap).
Filtering a tree (in the sense of excluding or including headings satisfying content-based critera) is one of the things missing in ndxcards. (Not nearly as important a possible addition, in my opinion, as hierarchical key words).
>So is
>there a 5th way to hide info?
>
>I seem to recall that Framework would show you what was on
>the *back* of a topic. (The data is in the front; I think some sort of script was on the
>back?)
>
>I guess showing and hiding columns could be a way too, though it’s a stretch.
Posted by Stephen R. Diamond
Aug 30, 2007 at 08:35 PM
One other default filter operation worth comment - Hide. I haven’t seen this in outliners, but the mind mapper VisiMap includes it. Whether it is a unique default filter, I don’t know.
Hide simply makes the selected items temporarily disappear—the most degenerate case, I suppose, of filtering. If it isn’t clear what I mean by a default filter—you select items, and then can optionally apply the presets such as collapse branch, expand branch, hoist branch, or hide branch.
So I think the most relevant answer to your question, David, is that an additional way of hiding items is by Hiding them. That’s a filter, but all these operations involve filters. The important distinction is whether filtering is based on content (data or metadata) or purely on position and selection status. Hide applies to whatever items are selected.
Posted by David Dunham
Aug 31, 2007 at 02:33 AM
Stephen R. Diamond wrote:
>double hoist (two independent heading hoisted at the same
>time -ADM) and hoist on hoist (hoist relative to hoisted headings - NoteMap).
OK, the first makes sense (though the way Opal defines focus excludes this). Though I suspect it makes more sense if the topics in question are sisters.
I’m not sure i understand the second. In Opal or MORE, you can focus, then focus on one of the still-visible topics. Unfocus goes back one level (I can’t remember if MORE had this but I think it did), to the previous focus. Is that what you mean by hoist on hoist—nesting?