This Week's Sponsor:

TRMNL

The E-ink Companion For Your Favorite Tools

Posts tagged with "automation"

Editorial Workflow for iThoughts→

I had a feeling it was only a matter of time before Rob Trew started playing around with Editorial. Rob is the author of some of the most amazing scripts for OmniFocus and mind-mapping that I’ve ever used, and now he has created an Editorial workflow to turn a Markdown document into a tab-indented list that can be pasted in iThoughtsHD. In iThoughts, you’ll end up with a nicely formatted mind map that respects the indentation of the original document. This is just another example of Editorial’s flexibility in the workflow system and Python scripting.

Side note: I still have to check out iThoughts’ new Mac version, iThoughtsX. I’ve just been too busy finishing an eBook and submitting it to Apple.

Permalink

Mirimage’s Editorial Workflows for Pocket and App.net→

Great demonstration of Editorial’s scripting capabilities. First, a workflow to fetch a random article from Pocket:

I’ve made 3 workflows; two for the authentication (Pocket Auth 1 & 2), and one that fetches a random article from the user’s unread queue and opens it in the Editorial browser. The Pocket authentication only needs to run once.

And then one to post on App.net (which could be nicely chained to my Post To WordPress workflow):

If you’re an App.net Developer, you can post to App.net directly from Editorial. I integrated this workflow into Federico Viticci’s Post to WordPress workflow, to post new articles to App.net in addition to Twitter.

Side note: I’m keeping track of Editorial workflows I find over at this Pinboard tag.

Permalink

Reinventing iOS Automation: Editorial Review

Editorial for iPad

Editorial for iPad

Update: I have turned this review into an interactive book with additional & exclusive content. You can find it on iTunes, on sale for a limited time. More information is available here.

Ole Zorn knows how to push the boundaries of iOS. His latest app, Editorial for iPad, redefines the market of text editors for iOS, and, in many ways, sets a new standard for iOS automation and desktop-class apps. Editorial makes me want to work from my iPad.

Before I get to the details, allow me to offer some backstory to properly contextualize Editorial and the process that led me to its launch today. I have been testing Editorial for the past eight months (since late November 2012, when I received the first beta build), and I’ve seen the app go through numerous iterations and changes. At one point I wasn’t even sure Editorial would come out anymore. Editorial has become the essential part of my iOS workflow, and it only seems fair to have a proper introduction.

Read more

Byword For iOS Gets Improved URL Scheme→

In a minor update released today, Byword developers Metaclassy have brought an improved URL scheme (based on x-callback-url) to the app, enabling actions for creating, opening documents, and manipulating text. Documentation is available here.

The actions supported by the URL scheme are:

  • new
  • open
  • append
  • prepend
  • replace

With these actions, you can now send text to a specific file in Byword, choosing to either create/open an existing document, insert text at the top (prepend) or bottom (append), or replace the entire contents of a document with new text. When using the Byword URL scheme, you’ll need to percent-encode text, which can be easily done using Launch Center Pro’s encode actions or Drafts’ double curly brackets.

This improved URL scheme creates some new interesting possibilities for iOS automation with Byword. I imagine many will experiment with workflows to append or create text from Mr. Reader’s Services menu, take notes with Drafts, or prepend text from Safari or Chrome using a browser bookmarklet. However, I still think that the URL scheme could be expanded to include support for triggering Publishing actions automatically, optionally supporting x-success to go back to another app after a post has been sent to a service integrated in Byword. With Poster no longer receiving updates, I believe the folks at Metaclassy have a great opportunity to keep Byword the simple and elegant iOS text editor that many love, while also adding advanced functionality that power users will come to rely upon in their daily workflows.

Permalink

Check Dev Center Status From iOS with Pythonista→

A great idea by reader Nicolas Hoibian, which uses BeautifulSoup to fetch the source code of Apple’s System Status page, parse it, and print it with custom fonts and colors in Pythonista’s console.

Here’s my modified version that uses Pythonista’s notification module to re-run the script every 6 hours by firing a local iOS notification on your iPhone or iPad (it assumes the script is named “DevCenter” in Pythonista).

Permalink

Resolve Short URLs with Pythonista on iOS

Clean URLs

Clean URLs

I don’t like it when third-party apps or services force me to share links to articles or webpages using their own custom shortened links. I understand the appeal of personalized short domains – after all, we tweet mcstr.net links with the @macstoriesnet account – as they can provide analytics to track clicks, can save characters, and, at least in theory, they “look cool”. However, I’ve been long considering the idea of dropping our mcstr.net links, but I think the issue is worse (and more annoying) for apps and services that don’t tweet links to their own content (like we do) but that override others’ links with different domains. An example is Pocket, which gives you the clean, original URL when you choose the “Copy Link” action from the sharing menu, but that instead returns pocket.co links when sending text to Drafts (which I do often). I’ve grown tired of this practice (in Pocket and other services), and I’ve put together a workflow based on a Python script that allows me to easily resolve short links without having to open the browser and tap on multiple menus. Read more

Editorial for iPad→

Ole Zorn is finally talking about his upcoming new app, Editorial, publicly on his website:

I tweeted earlier today that I’ve registered the name for a new app in iTunes Connect. It’s called Editorial, and I’ve actually been working on this for over a year now.

At its core, it’s a Markdown editor for iPad, but you can also think of it as a Pythonista spinoff, or a workflow automation tool, not unlike Automator.

I say “finally” because I have been testing Editorial since November 2012. All my reviews have been written and edited with Editorial; I have built workflows that, for me, make working with text on the iPad better than using Sublime Text 2 on my MacBook Air. When I’m on my Mac, I miss Editorial’s automation and editing features. And if I haven’t posted a screenshot of my iPad’s Home screen in a while, it’s because I had Editorial in my dock and I couldn’t share it.

Ole Zorn is the developer of Pythonista, which I have written extensively about. I can’t wait to share more about Editorial.

Permalink

IFTTT for iPhone: A Different Kind of iOS Automation

IFTTT for iPhone

IFTTT for iPhone

I used to heavily rely on IFTTT for my daily automation workflows that involved appending bits of text to files in my Dropbox, forwarding tweets to my OmniFocus inbox, generating PDFs, or archiving Instagram photos to my Dropbox account. IFTTT, acronym of If This Then That, is a web service that lets you connect other web services together to create automated workflows that run every time a piece of data is triggered: by leveraging a variety of APIs from compatible channels (such as Facebook, Dropbox, Evernote, Feedly, and more), IFTTT lets you automate the web in powerful (and sometimes unexpected) ways. Browsing Popular recipes on the IFTTT website can give you an idea of the scope of web automation that’s made possible by the service, and we’ve covered IFTTT in the past on MacStories as well.[1]

However, I stopped depending on IFTTT because, once I got more comfortable with my own Mac mini server as a remote automation assistant, I wanted to control the pipes of my personal data. I’m still using IFTTT for things like receiving an email if it’s going to rain tomorrow or a new SMS for press releases published by Apple (just an example of the power of IFTTT channels and recipes), but it’s not the primary system that I rely upon for automating daily tasks. The new IFTTT app for iPhone, which I have been testing and has been released today on the App Store, may make me (partially) reconsider my decision. Read more

Getting Safari’s Selection on iPad As HTML With A JavaScript Bookmarklet→

I modified this bookmarklet posted by “Tim Down” on StackOverflow to send selected text from Safari to Drafts as HTML. The result is the following code:

javascript:(function(){var%20h="",s,g,c,i;if(window.getSelection){s=window.getSelection();if(s.rangeCount){c=document.createElement("div");for(i=0;i<s.rangeCount;++i){c.appendChild(s.getRangeAt(i).cloneContents());}h=c.innerHTML}}else%20if((s=document.selection)&&s.type=="Text"){h=s.createRange().htmlText;}window.location='drafts://x-callback-url/create?text='+(h);})()

So let’s say you want to grab the first paragraph in this post. Normally, in Safari for iPad you’d end up with the plain text fetched by window.getSelection:

This is a fantastic report with lots of data points for any developer trying to get their apps featured by Apple. Dave Addey’s highly interactive regional graphs and notes are very well done. Be sure to check out Dave Addey’s other works on his main blog.

As you can see, formatting and hyperlinks have been removed. With the bookmarklet above, you’ll receive the HTML version of the selection – which looks like this. But what’s the point?

My idea was that I wanted to be able to automate the process of capturing rich text from iOS’ Safari; I wanted to achieve the same kind of functionality I have on the Mac, where rich text can be dragged from Safari or Chrome and dropped into Evernote, preserving styles, hyperlinks, and images. I thought that combining HTML output with an Evernote Append action (with the “Send as Markdown HTML” option turned on) would let me receive valid HTML content in Evernote starting from an iOS workflow. And, for the most part, I was right, because the workflow does mostly work.

As it turns out, Evernote is extremely cautious with the HTML tags they accept, and the ones that are supported follow the XHTML guidelines as ENML is a superset of XHTML. This means that my bookmarklet will work for something as simple as selecting a single paragraph, but may easily fail with multiple selections, inline images, complex styles, and so forth. When that will happen, Drafts will return an error when trying to append HTML to Evernote; obviously, this will work just fine with Dropbox, which doesn’t care about the kind of text you’re using in your actions. Even better, this should work very well with Textastic’s just-released update that supports x-callback-url.

I guess the solution would be to build a Pythonista-based converter for Evernote-approved XHTML tags and place it between Safari and Drafts, converting HTML tags Evernote won’t like to compatible ones. If you’re interested, my birthday is August 10.

Permalink