It’s welcome news to hear OmniOutliner 6 is on its way to release. I was afraid OmniGroup didn’t put a priority on it.
Conventional word processors have lost their luster, which is terribly unfortunate. When I roll up my sleeves and write in earnest, there’s nothing better - my opinion, of course - than either my favorite word processor or a Markdown-driven workflow with a powerful text editor, BBEdit or, ghastly as it sounds, vim.
Outliners may be in the same boat with conventional word processors. There are too many more flexible options for outlining. Devonthink, Curio, Obsidian, Notion, Tinderbox, and a zillion other organizational tools will work well for story planning.
Like word processors, outliners still have a place. OO’s customizable columns open some nice possibilities, too.
For instance, set up OO columns for the fields in an Aeon Timeline file. A CSV export from OO will import directly into Aeon without editing.
“Plottr mode” is possible. Add a column called Thread and filter on that.
In spite of all the flexibility and hipness of more complex utilities, I’m still happy I’ve got OmniOutliner.
It would have been nice, though, to see a good old fashioned paradigm-buster. For instance, a mind map view or a story card repo. Imagine writing cards, like Plottr, in a library area, not in the outline. In outline view, either write nodes or pull in some of those story cards.
While we’re dreaming, let a story card appear in more than one place. It might be convenient to focus on chapters in outline view and see your McGuffin story card in each chapter in which it plays a part.
Curio will already do that. Make your story cards one-liner text figures with notes attachments. In a list or outline object (figure, in Curio-speak), copy the McGuffin story card as a synced text figure. There you go. An outline node pulled from a library of otherwise lost ideas.
