any experiences to share on making such a transition away from OmniFocus
I’m probably not the best person to comment – I have made that transition, but the scripts and plugins which I’ve drafted clearly happen to fit my own workflows well.
I do know of one other user who is probably better placed to comment, and is planning, I think, to make some video material on the (still evolving) txtQuery tools.
(Which I use to generate custom perspectives (across several files) with sorting and grouping, and with links back to the original lines in FoldingText files).
Broadly, however, every tool has a slightly different profile and niche. OmniFocus seems to be targeted at people who are heavily dependent on synching with a smart-phone, and are happy to fill out and see a fairly limited set of forms and perspectives. As it happens, although I sometimes do a bit of work on a local wifi iPad, I’ve put aside smartphones now ( ‘enough, already …’ was my feeling : - ) so I haven’t done any work on synching. Others seem to be mainly using Dropbox, and one of the scripts here can add links (in Reminders.app notes) to lines in iPad for Editorial files.
Plain text work flows, with links to Reminders.app (and more deeply customisable perspectives) are probably best where notes are central and need to be highly flexible, and where rigid distinctions between scheduling and work can be a bit encumbering or complicating.
It’s a more work-centred and less shepherded approach. For me, the key benefits are speed and integration with document production. FoldingText combines the best of of OmniOutliner and OmniFocus together, drops all their widgets and inflexibilities, is more deeply and reliably scriptable, picks up a lot of speed, and adds a powerful kind of outline-aware filtering which neither of them has.
For me it happens to be a perfect hub for gathering thoughts and shaping them into documents and schedules, at every level of scale.
It works particularly well, of course, in conjunction with Brett Terpstra’s Marked 2.