Dave Winer has been developing outliners for his entire professional life. Not surprisingly I’ve been working in outliners my entire professional life. First with ThinkTank on the Apple ][ (a Winer product); then ThinkTank and MORE (both Winer products) on the Mac; and now OmniOutliner Professional (an Omni Group product) on the Mac.
Almost everything I do with text on the computer begins life in an outline. For example, this article originated and was roughed out in OmniOutliner Pro, then migrated to BBEdit for any necessary HTML markup, and finally copy-and-pasted to ExpressionEngine—the content management system on which ARTS & FARCES internet runs.
My project notes, books, articles, wikis, and other manuscripts all start as outlines.
For almost as long as I’ve had a website—sometime around 11 January 1993, when the domain was registered—I’ve wanted to be able to easily publish my outlines on the web. By “easily publish” I mean with one click. Yeah, I’m lazy. One click.
Before you hit that “report an error” link at the bottom, I know all about OmniOutliner Pro’s two HTML export functions. The dynamic option is the most useful, rendering a static HTML page with an accompanying JavaScript file and set of icon images for bullets, tip-downs, and checkboxes. But once it’s in the browser, it’s read-only.
Now comes Winer’s newest company—Small Picture, Inc., a collaborative endeavor with Boston-based Kyle Shank—with a fully dynamic and interactive JavaScript outliner that works in any HTML5-compatible browser. Small Picture is unveiling its outliner in a rolling unveil. Each Monday, another piece of the puzzle is released and the picture comes more into focus.
Here’s what I’m hoping for with Small Picture’s outliner: Full-blown support for importing and exporting Outline Processing Markup Language (OPML) files. With one click. And then an easy way to embed the server-side JavaScript in Apple’s OS X Server wiki module. Both should be easy-peasy. OPML is, after all, another Winer creation and it should be a simple matter to call the JavaScript file from within the wiki module of Apple’s OS X Server. Oh, and I’d also like for it to be really small and efficient.