Do some outlining. Then outline some more…

I once more had to realise that when the writing is not going well, it might be because I haven’t figured out what I wanted to say, meaning that I probably need to do more outlining. So here is my freshly rediscovered rule of thumb: “when you’re stuck, when you got the writer’s block, just do some outlining. And then outline some more. And then some more.” And then you will know what to write about and how to organise your thoughts. In fact outlining is not only about developing the content but also deciding the order in which the content is going to be presented, i.e. the flow of logic, the order of presentation, and the structure of the content. All the more reasons to do some outlining, and then outline some more.

Using Natara Bonsai with WorkFlowy

Natara Bonsai has long been my favourite outliner, but in the last couple of years it has been gradually displaced in my daily use by WorkFlowy, mainly because WorkFlowy syncs automatically and seamlessly across all my devices using different platforms, which is very useful for capturing notes and todos and having them always available.

Nevertheless, there are situations where Natara Bonsai is still my go-to choice. For example, when I need to organise, analyse, sort and resort large lists, or when I need to hierarchically structure some complex information, where it helps that different hierarchical levels can be displayed in different colour, to guide the eye.

Fortunately it is very easy to get information from Natara Bonsai back into WorkFlowy. All you need to do is install the OPML export template from the CarbonFin website (instructions available there), then export the Bonsai outline as a .opml file, open the .opml file using your favourite text editor (for this task I like to use Notepad++), and simply copy and paste the contents of the .opml file directly into a WorkFlowy bullet point. WorkFlowy will not only preserve the outline hierarchy but it will also display any Bonsai outline item notes as inline WorkFlowy notes.

Here is a Bonsai outline (the final bullet point has a note, displayed in the pane on the right):


And here it is after having been pasted into WorkFlowy (note the inline note under the last bullet point):



Frank Degenaar points out in the comments section that it is possible to add colour to a WorkFlowy outline as well, using the “Painter for WorkFlowy” Chrome add-on and some stylesheets using the “Stylish” add-on. That is definitely true and I do make use of those tools in my WorkFlowy all the time. It would only take me a minute or two to reconstruct the colour scheme of the above Bonsai outline in WorkFlowy, and the two would look fairly similar (especially if I change the dark WorkFlowy theme to a light one).

However, the colouring-in capability of Natara Bonsai works quite differently from that of WorkFlowy and serves a different purpose. You can set up Bonsai so that it automatically colours in your outline items according to the outline level position they occupy. This means that if you promote or demote an outline item, its colour will change accordingly and automatically.

While it is possible to retrospectively colour in a WorkFlowy outline by adding a colour tag to each item individually and manually (which would be time-consuming in the case of very large and multi-level outlines), these colours will not change when you demote or promote these items, as their colour tags will travel with them.

The  key point here is that when using Bonsai, the colour scheme has already been set up as default (using the procedure I described earlier), so I don’t have to pay any attention to the colouring-in, it just works automatically as I type away and keep promoting and demoting items. In contrast, with WorkFlowy the colouring-in needs to be done manually, individually for each item, and retrospectively, after the item has been added, and it does not change, if I move the outline items, thus breaking the logic of the “colour by hierarchy level” scheme.

This difference becomes significant when you want to work on large and complex lists and you want to pay attention to the text, rather than be disrupted by the mechanics of colouring-in. Bonsai just allows you to work faster, without having to make decisions about and fiddle with every single item, as you would have to in WorkFlowy.

By the way, as I have already explained in that earlier post, it is possible to use other criteria for the automatic colouring in Bonsai, such as category, priority or due date.

Natara Bonsai downloadable from the Internet Archive

I still get visitors coming to this site looking for the outliner Natara Bonsai almost daily, as I mentioned it occasionally that it was one of my alltime favourite pieces of software. Unfortunately the Natara Bonsai download page went down sometime in 2014, never to come back again. There is now only a placeholder page for the main Natara site that points to the Natara blog (the last post on which dates 6 June 2013).

A few months after the Bonsai site has disappeared, I stumbled upon some kind of a mirror site at where it was still possible to download the software from. I was very happy to share that link, and I got a few emails from Bonsai fans thanking me for it. Apparently Bryan Nystrom, the owner of Natara Software, Inc., was kind enough to sell them a licence.

Alas, a few months ago this mirror site has also gone down. It seemed that Natara Bonsai was well and truly gone. I was kicking myself for not having taken some screenshots of that site at least, just as a keepsake (yes, that is how much I love this software). Then one day it occurred to me: what if there are some archival pages of the Natara site on the Internet Archive? And lo and behold, there indeed are a number of such pages. And not only that: the Bonsai files can still be downloaded from there! Here is one such link for instance:

I cannot vouch for the safety of these files, so download and run them at your own risk. But chances are they might just be the original Natara Bonsai files. So fellow Bonsai fans, rejoice!


Latest enhancements to my ConnectedText ‘ecosystem’

Actually I’ve used these tools for some months now, I just haven’t had a chance to mention them on this blog. I use the two in conjunction with each other, so it makes sense to mention them together.

The first tool is a software called TaskSpace. The need arose for this one with the introduction of the floating windows feature in ConnectedText v. 6., which allows you to open an unlimited number of CT ‘topics’ (documents). If you work with a multi-monitor setup (and even if you don’t), there comes a point where you might have several floating windows open, which you would need to move around individually (in my case from one monitor to another), which quickly becomes a hassle. Moreover, floating windows come into focus every time you have the main CT application in focus, meaning that the floating windows would obscure whatever other app window you might want to look at in the other monitor while looking at the main CT window.

TaskSpace solves both of these problems. Firstly, by using the handy CTRL+SHIFT+M combination, you can send individual CT floating windows to a single TaskSpace window, where you can further organise them into rows and columns, and then move them around the various monitors as a single window. It is also possible to create tabs within TaskSpace, so you can add as many CT floating windows to it as you like. Secondly, the paid-for version of TaskSpace also gives you the option to change the behaviour from “always on top” to “normal” etc., which I presume would disconnect the floating windows from the main CT app, making it possible to view them independently (and hide them from view at will). I say “presume” because I’ve never tried that feature. I use a comparable feature that comes with Direct Folders, where you just right-click on the close button of any window (except Chrome, with which it doesn’t work for some reason), and the window changes from “normal” to “always on top” and vice versa.

Here is a screenshot of a TaskSpace window with three CT floating windows docked:

TaskSpace_with_CTThe second tool is a piece of hardware called Boogie Board Sync, which I use almost exclusively with ConnectedText, by creating handwritten notes, syncing them via Bluetooth to my PC, converting them from PDF to .PNG files in PDF-Xchange Editor (which allows you to semi-automate the process by setting up the file names and desired image resolution), and dropping them into CT. Then I use TaskSpace to view these handwritten notes as CT floating windows in one monitor, while working away in CT in the other monitor. I use Boogie Board Sync mainly to capture ideas concerning my main writing project quickly (especially when my PC is not turned on), and then I tick them off in CT eventually, once the work recorded in the BB Sync file has been done.

BB_SyncIf you are a CT user and you are still looking for a Christmas present for yourself, I can highly recommend the BB Sync. But make sure to read the Amazon USA etc. reviews about it to understand its limitations. Many customers seem to have unrealistic expectations about it, and then they complain that BB Sync didn’t meet them. However, if you read carefully what BB Sync offers, and you’re happy with those limitations (such as the inability to recall notes on the device itself – saved or deleted notes need to be synced with the PC to be viewed), then BB Sync can become an invaluable tool for getting handwritten notes into a PC quickly, and into ConnectedText in particular. There are of course many other possible use case scenarios, such as e.g. using BB Sync to write handwritten diary entries and then using the date topics feature in ConnectedText to build a handwritten journal.

Most recent process flow for academic writing

Just for the record, I thought I’d repost my comment here that I’ve just left on Christian Tietze’s blog concerning on how I go about outlining and writing on the back of Zettelkasten notes these days.

My latest process flow on Windows 7 for academic writing, using 3 monitors, so some of this software could be viewed simultaneously:

1) read the literature (usually PDF articles or books);

2) take reading notes (mainly quotes + interpretation) in ConnectedText as Zettelkasten;

3) use VUE to develop a concept map to make sense of the material, while reviewing the CT notes in floating windows (i.e. multiple notes can be viewed simultaneously);

4) develop an outline for the paper in a Freeplane mind map, building on the VUE concept map and adding hyperlinks to selected quotes and notes in ConnectedText, so they can be easily called up when writing about a given point;

5) write in plain text using Markdown in WriteMonkey (distraction-free writing software), while checking off nodes in the Freeplane outline as they get written up, and paste in raw EndNote code for academic references, where necessary;

6) paste draft into Outline 4D (single-pane outliner with inline notes) and reverse outline it, i.e. add a heading to each paragraph to see the overall logical structure and content of the paper, and edit it accordingly to improve coherence, eliminate redundancy etc.

7) Import into MS Word, do final editing, add final headings, table of contents, and convert raw EndNote code into formatted references and bibliography.