jaethin.blogg.se - Omnioutliner templates

#OMNIOUTLINER TEMPLATES SOFTWARE#

If in June I see an article which can be used in a course taught in November I will likely drop the reference in the OmniOutliner file for that course. Something that can sit and ‘cook’ for a few weeks or months is an OmniOutliner thing. OmniFocus is for recording the results of such thinking so that they pop-up on your lists at the right time.Ģ) What is the timeframe of action? Something that needs to be clarified and dealt with during the next week or two belongs in OmniFocus. OmniOutliner is for logical thinking through the project. More open-ended ideas go into OmniOutliner. When I encounter an idea or another ‘input’ for future action I choose between OmniFocus and OmniOutliner based on a few criteria:ġ) How concrete and actionable is the input? Concrete and actionable things go into OmniFocus (unless they belong to TaskPaper, which is for very simple lists of corrections to a manuscript or things to discuss with the boss). I use OmniOutliner for the events I organize, courses I teach and larger projects that I coordinate. (Another 10–15% are outlines of presentations and talks and the rest are writing outlines in fact I have OmniOutliner templates: Plan, Presentation and Manuscript). I have over 50 project plans which is about 1/5th of all my OmniOutliner files.

#OMNIOUTLINER TEMPLATES SOFTWARE#

My favorite software so far has been OmniOutliner. It makes a lot of sense to keep these items separate from your concrete next actions. Where should one keep project plans if not in OmniFocus? There is actually no good answer to this question. As a results they may contain a lot of open-ended items possibly only relevant in distant future and which are not necessarily your responsibility. In contrast, project plans should be systematic and comprehensive, they should not miss certain things just to spare your attention. Contexts, start dates, ‘on hold’ options, perspectives, sequentially organized projects, and other features of OmniFocus help filter out unwanted information and focus your attention on next actions. In the GTD terminology these are called “next actions”. OmniFocus is designed to provide an unambiguous list of concrete things that both should and can be done. If ( of the five things that should be kept out of OmniFocus are project plans. Note that the script uses the byName() instance function to both check for the existence of the style, and to generate a reference to the style instance.

Returns the single named style with the specified identifier, or null if no style has that identifier.Īnd here’s a variation on the previous script that generates a reference to a style instance that is created if it doesn’t already exist.

Returns the first named style that has the specified name, or null if none do.īyIdentifier(identifier:String) -> NamedStyle or nil.

forEach( function( nStyle))īyName(name:String) -> NamedStyle or nil

Omnioutliner:///omnijs-run?script=document%2Eoutline%2EnamedStyles%2Eall%2EforEach%28function%28nStyle%29%7BnStyle%2Eremove%28%29%7D%29 Delete All Named Stylesĭocument. The name of the style that is presented in the interface.

A unique identifier for the style, which is suitable for long-lived references.

Returns a NamedStylePosition that indicates the slot before this item.

Returns a NamedStylePosition that indicates the slot after this item.īefore (NamedStylePosition r/o).

The following are the basic properties of the NamedStyle class:Īfter (NamedStylePosition r/o) Using Omni Automation, you can create and apply named styles in your outline documents. Many outline documents created using the provided templates, include sets of named styles by default, such as: Heading and Highlight Named Styles are defined sets of style attribute values that are user-assigned to characters, words, sentences, paragraphs, or rows. As documented previously, Level Styles are defined sets of style attribute values applied to rows based upon the row’s position (level) in the outline hierarchy.