Forum Posts Feed
UV Outliner Now Supports Columns
< Next Topic | Back to topic list | Previous Topic >
Posted by Pierre Paul Landry
Jan 27, 2010 at 04:25 AM
What separates one-pane outliners from 2 (or more)-pane outliners, can be summarized in 2 lines:
- Allow writing text in an outline form
- Allow expand and collapse of sections of this outline (expand/collapse items show/hide their sub-items)
(this excludes folder panes, document trees, and HTML/RTF editors)
Posted by Alexander Deliyannis
Jan 27, 2010 at 04:30 AM
I also don’t want to counter any enthusiasm, especially on the part of Fedir the developer, but I think that the claim that UV Outliner is “the first modern single pane outliner for Windows with multiple column support in the world” (taken from the blog) is taking things too far. InfoQube is such a modern outliner with multiple column support, as is ListPro http://www.iliumsoft.com/site/lp/lp_ssh.php
That said, I’m glad for my own initial CRIMP enthusiasm on this product; if development continues at this rate, it will probably have several unique features by the end of 2010.
Posted by Lucas
Jan 27, 2010 at 05:08 AM
Pierre Paul Landry wrote:
>What separates one-pane outliners from 2 (or more)-pane outliners, can be
>summarized in 2 lines:
>
>- Allow writing text in an outline form
>- Allow expand and
>collapse of sections of this outline (expand/collapse items show/hide their
>sub-items)
>
>
>(this excludes folder panes, document trees, and HTML/RTF editors)
>
Right, that’s the conventional definition. I’m just wondering whether “one-pane outliner” is the most useful term to describe the functionality of writing hierarchical/collapsible text. The way I see it, there are three basic possibilities in terms of the functionality of most conventional outliners:
1. Hierarchical folder/title structure *and* hierarchical/collapsible main text
2. Hierarchical folder/title structure but *no* hierarchical/collapsible main text
3. *No* hierarchical folder/title structure but *does have* hierarchical/collapsible main text
According to the conventional definition, both number 1 and number 3 are “one-pane outliners”, while number 2 describes “two-pane outliners.” And yet, both numbers 1 and 2 both have two panes, while only number 3 in fact has one pane.
So the key distinction isn’t between one and two panes; rather, it’s between outliners that offer outlining in the main text area versus outliners that offer it only in the folder/title area.
Am I making any sense?
Posted by Chris Thompson
Jan 27, 2010 at 05:49 AM
I think your proposed taxonomy is more confusing than anything. One pane outliners are outliners that are designed primarily to edit outlines in a single, integrated window. There may be support for additional notes attached to items, and it may be possible to turn on a window, pane, or inline text display showing those notes, but that secondary pane shouldn’t be a primary feature of the user interface, otherwise you have a two pane outliner.
Mori is either a two or three pane outliner depending on one’s classification scheme. The difference between two and three pane outliners isn’t particularly significant in my view, because once you have to start having to edit your outline in disjoint parts of the user interface, whether there are two or three panes doesn’t matter.
In any case, the developer of UV Outliner deserves huge kudos for his work here. One shouldn’t forget InfoQube though, as it still has a more complete set of traditional outliner features, including clones and hoisting, in addition to columns. But the interface is a bear. I have no doubt UV Outliner will add hoisting at some point. If the developer adds clones, it will be a giant of a program.
—Chris
Posted by Chris Thompson
Jan 27, 2010 at 05:49 AM
I think your proposed taxonomy is more confusing than anything. One pane outliners are outliners that are designed primarily to edit outlines in a single, integrated window. There may be support for additional notes attached to items, and it may be possible to turn on a window, pane, or inline text display showing those notes, but that secondary pane shouldn’t be a primary feature of the user interface, otherwise you have a two pane outliner.
Mori is either a two or three pane outliner depending on one’s classification scheme. The difference between two and three pane outliners isn’t particularly significant in my view, because once you have to start having to edit your outline in disjoint parts of the user interface, whether there are two or three panes doesn’t matter.
In any case, the developer of UV Outliner deserves huge kudos for his work here. One shouldn’t forget InfoQube though, as it still has a more complete set of traditional outliner features, including clones and hoisting, in addition to columns. But the interface is a bear. I have no doubt UV Outliner will add hoisting at some point. If the developer adds clones, it will be a giant of a program.
—Chris