My top requests for OmniOutliner Pro > 3.0

[jmck at mac.com]

On Thursday, January 13, 2005, at 11:50  AM, Christian Roth wrote:

> jmck at mac.com wrote:
>
>> Coupled with request one, I would be able to add a top level "action
>> items" to collect things that need to get done next, while also 
>> keeping
>> them correctly filed as children deep within "design review."
>
> Just out of curiosity:
>
> How should a single section consisting of clones from sections with
> different column layout be handled (both visually and conceptually)?
>

Gahh, great question, to which I have no perfect answer. For the uses I 
have in mind, I would be happy only seeing the main "topic" column 
displayed in the clone-row, if I could have a pointer to take me to the 
originator of the clone. Of course, checking off the checkbox in either 
the clone or the original should update everywhere.

In fact, if we do this, the cloned items could take on their own random 
columns. So, I could have project specific parent sections with these 
columns:

task	owner  date due

And one place I might want to collect clones could be in another parent 
element called "post mortem analysis" which had these columns:

task	successfully achieved? notes

Editing the "task" column value would update the clone and the 
original; editing any other column would not.

This is much like a standard relational database, AFAIK.

I do consider the topic-specific column request to be much less 
important than the cloning request...

>

John McKenzie