I remember my own joy upon installing an application that had no user When every user’s “applications” were unique to their own imaginations Many of us really believed that promise, and looked forward to the day Tied together in intimate ways, almost synthesizing new applications. It’s all that wonderful promise we hoped for more than aĭecade ago when the concept first appeared-that applications could be “Scripting” in this context means more than controlling a singleĪpplication. Relationship between scripting and outlining. Frontier was the first scriptingĮnvironment for the Mac, appearing well before AppleScript! Dave is aĭifficult man, but I surely must give him credit for seeing the intimate We mentioned Dave Winer’s creation of Frontier. InĮarly ATPO columns we traced the history of outlining and along the way The first is in the way it integrates with the environment. Than what DEVONthink offers, which is still leagues better than Apple’s Knowing Michael’s background and hisĮxperience with SpamSieve, I would expect some very capable semantic I expect users to ask for these things,Īnd for C-Command to respond. It has some prebuilt smart folders and columns, but A recent version justĮagleFiler is missing stuff we celebrate here at ATPO, stuff such as It has a useful “semantic grouping” assistant thatįinds internal structure based on matching words and phrases, allowingĭEVONthink users to edit and create material. It has no way toīuild structure and relate items, so it isn’t interested in outlines.ĭEVONthink is at the other end of a spectrum. That the developer’s mother can see all the way through it. Note-taking applications where the user is expected to create and evolve Thatĭifferentiates this class of outliner from more writer-oriented and These applications it is intended to be relatively static. In terms of market, it competes in some way with Yojimbo and DEVONthink.īoth of those are repository-type applications with special attention Generally outline what it is and then just focus on a few elements of Reviews far more useful to you than this brief mention in ATPO. I think there will be a lot of attention given to this application, with The applications I propose to draw from are: Talk about writing without starting with the actual writing process and Many ATPO users are in the outliner communityīecause they use their outliners in workflows that produce some written But I’ve had many requests to address writing, and it Pretty strict about what we discuss here and at drawing the line around Where we are deviating from the ATPO model is that many of theĪpplications we’ll look at don’t use outlining. Redo the list, show examples, and give some discussion. Some time to set me right, correct, and add things. List of the products we’ll draw from for our examples. Things I suppose should be on a list of capabilities to consider.
We’ll do that now with writing environments, or at least begin to. Or bug the heck out of a developer to add a certain capability. Than another, it would be better to note what the various capabilities wereĪnd let readers decide which might suit them, and then follow the So rather than talk about whether one product was better The idea was that outline uses varyĪll over the place, and outliner users are often highly individual in Then we gaveĮxamples from existing outliners.
That listed the types of things that an outliner might do. To judge from the links to past columns, the most popular ones are those This ATPO, we go back to our roots in one way, and stray in another.