Re: OmniOutliner Pro 3.0

< Next Message | Back to archived message list | Previous Message >

Note: This message is from the outliners.com archive kindly provided by Dave Winer.

Outliners.com Message ID: 2527

Posted by stephenz
2005-01-12 14:51:43

> Some of the things you would do with columns, such as the story, I would prefer to use clones. I guess the best practice would depend on whether you anticipate further grades of classification, e.g. groupings by kinds of character roles.

I love cloning for many purposes; however, in a story outline, or even a project outline either of which is based upon a series of related steps, cloning may not be as effective because it breaks the chronologic flow of the outline, and inserts duplicate items. In listing the tasks in a project, for instance, I don’t want to view the same task twice, at least not when overviewing the project as a whole. Which isn’t to say that also having cloning in addition to columns wouldn’t be a good thing.

Being able to view meta-data in columns also has the advantage, if properly implemented, of allowing you to sort on the column, so you can restructure the flow of your outline based on different criteria. I.e. if your outline has a column for start dates and another for due dates, you can quickly re-sort your data to see either of these in chronologic order. I’m not sure you can get that kind of quick response from clones.

Of course, the column advantage I’ve just mentioned isn’t restricted to single-pane outliners.

Steve Z.

Back to archived message list