5/25/2023 0 Comments Taskpaper buy![]() Or you could build a workflow which publishes the status of all the tasks in a project. You can also use the time estimates and dates already entered into OmniFocus to schedule tasks on a calendar. You can then run a workflow that processes those placeholders and builds a new project (such as “Run a marathon on June 30”) from that project template, and these project templates and their processing workflows can be shared with others.īut that’s just one possible workflow which is enabled by automation. This means, for example, that you can now create a text file outlining an entire project, with placeholders for specific names, defer dates, due dates, and so on. But we didn’t just add support for two-way communication between OmniFocus and other apps, we added support for doing for automating a whole lot more of the powerful capabilities of OmniFocus. At its simplest, this means that you can create a workflow that adds more than one item to OmniFocus. With OmniFocus 2.14, I’m very pleased to be able to say that OmniFocus now includes best-of-class support for callback URLs. Using those apps you can build automation workflows that no longer stop the moment you transfer control to another app: when that app finishes its work, it uses a different URL to “call back” to the next step in the workflow. Many apps-like Workflow, Editorial, Drafts, 1Writer, and Ulysses-now support two-way communication by through the use of “callback” URLs, as proposed at. Since 2008, the device hardware and the iOS operating system have both evolved significantly, and on most devices it’s now possible to have multiple apps running at the same time (one in the background)-and on some devices, you can even have two apps simultaneously running side-by-side.Īnd over those eight years, the app ecosystem has evolved as well. ![]() Well, how time flies! Fast forward eight years. And many apps have taken advantage of this primitive mechanism from 2008 to send a new task to OmniFocus or to ask OmniFocus to show a particular item or perspective. But even that much was quite useful: for example, you could add a Safari bookmark which would send the current web page to OmniFocus. Back then, URLs were considered one-way mechanisms: one app could send something to another app, but that was it: the original iPhone would only run one app at a time, so the starting app was gone and would never hear anything back. OmniFocus included support for automation through URLs on the day the App Store first launched, back in 2008. These are much like the URLs you enter into a web browser (in fact, you can enter these exact URLs into a web browser if you wish) and provide a mechanism for an app to transmit information to another app. In iOS, the primary way that apps talk to each other is through URLs. So watch today’s video to see me walk through using the excellent Things3 Parser with Taskpaper formatted notes in Drafts so that you can have a task template you can actually read and adjust without going cross-eyed.OmniFocus 2.14 improves automation by adding support for two-way communication with other iOS apps. The answer to all those questions amounts to, it’s super hard to do and you’ll miss more things and forget an existing task while you try to add another one. ![]() ![]() That same list looks like this in a Things3 URL scheme: things:///add-project?title=ski&when=today&to-dos=eden%20mask%0Alorelei%20mask%0Aarwen%20mask%0Acurtis%20mask%0Acynthia%20mask%0Aski%20helmets%0Askis%0Aski%20boots%0Apoles%0Agloves%20bag%0Acoat%20bin%0Awater%20bottlesĬan you even tell which task I intentionally left out? Could you add a task easily in the middle of that URL? How would you reproduce the list easily using the Things 3 URL Scheme builder? Take a look at the Taskpaper formatted project to make sure we don’t forget anything when we go skiing. Working with Taskpaper files is so much easier than Things3 URL schemes, because it’s far easier to read Taskpaper format than a URL scheme. Things Parser uses TJSContainer to take Taskpaper formatted files and turn them into projects and tasks in Things3. The need to detect which device you’re on sucks and Cultured Code needs to come up with some fix for this, until then Drafts and specifically the Things Parser helps clean this up so much. While Things3 has a solid URL scheme I’ve talked about a few times, it’s a huge pain in the ass to use when you need to adjust templates or deal with automation on iPadOS and iOS.
0 Comments
Leave a Reply. |