![]() I'm always encouraged to see an app that honors that arrangement from the get-go. If you do this stuff long and diligently enough, you eventually learn that when it comes to "task lists" you need to focus a lot more on the "task" than the "list" ( cf.). But, I'll be keeping an eye on this, and - if you struggle with rethinking your workflow around over-engineered productivity apps - I encourage you to grab a copy. This is very young software, and Jesse assures us that it still needs some TLC before being ready for battlefield usage (context views are being balky, for one). TaskPaper's easy tagging and fiddle-resistant stoicism could make it a go-to app for the overwhelmed knowledge worker (who's not quite ready to make the leap into the shell). What a lot of folks need is not the taxonomical rabbit hutch of The Big GTD App™ - they just need an easy way to structure tasks in a non-fiddly way. You can also assign contexts (such as "home", "office", or "car") to your tasks so that you can later generate lists of all tasks assigned to a specific context.Īs Gina Trapani has shown, there's clearly a place out there for a smart, text-y task app. It's simple to reorganize the list, create new items, mark items as done, and delete items that your finished with. ![]() TaskPaper makes it easy to create a list of your projects and their tasks so that you always know what needs to be done. TaskPaper starts with the simplicity of text files then adds just a bit of Mac magic to make it both smarter and prettier, but without giving up portability and ease of use. Run the workflow, answer the prompts, and you get a sub-project for the tasks added to your inbox.Jesse Grosjean from Hog Bay Software has just begun sharing the first releases of a new task-tracking app which adopts a refreshingly stripped-down approach to managing action on a Mac. Plus, OmniOutliner is plagued by feature bloat that makes it hard to use well. OmniOutliner files, by contrast, are basically OPML/XML readable by multiple apps, but not as plain as I’d like. Using it on iOS is the same as running the script on a Mac. TaskPaper is not a real outliner more than a couple of levels of indentation and things start getting unmanageable but its files are plain text. This was a complete rebuild of the code in Workflow. The other script I moved over was the "Read Book Tasks" script. All I have to do is open the template and run the workflow. In Editorial I simply pasted the project into a new Taskpaper file and I'm set. Navigate to the project you want to use as a template, tap the Share button, and copy it. I'm using his workflow unedited and found it really easy to recreate my templates on iOS. Ken Case shared an Editorial workflow that takes a template project in Taskpaper format and adds it to OmniFocus. Combined with Editorial or Workflow, this thing is awesome! It allows me to port two of the AppleScripts I use over to iOS. ![]() Omnifocus://x-callback-url/add?x-success=drafts4://&name=]¬e=]&project=Blog%20Post%20Ideas&context=Running&autosave=true Here's the URL I'm using to add new Blog Post Ideas: Thankfully, the Omni Group introduced this feature recently and I can now add items directly to OmniFocus on iOS and come back to Drafts without any extra steps. My current structure uses the Auto-Parser which allows Drafts to send tasks to the app without the need to confirm or edit an item. The main piece I found missing was the "autosave" parameter to the /add URL. The abilities of the new URL Scheme are exciting but there's still quite a bit missing from the structure as it stands. I have been hesitant to adopt the new automation methods in OmniFocus for iOS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |