This Week's Sponsor:

Kolide

Ensure that if a device isn’t secure it can’t access your apps.  It’s Device Trust for Okta.


Search results for "editorial"


Editorial 1.1: Another Step Forward for iOS Automation

Editorial, Ole Zorn’s text automation tool and Markdown editor for iOS, has changed the way I work on my iPad.

Combining an elegant text editing experience with a powerful workflow system based on actions and a built-in Python interpreter, Editorial reinvented iOS automation and explored new horizons of what could be achieved with inter-app comunication on an iPad. Editorial can be just a text editor, but its true potential and versatility are revealed by an Automator-inspired interface that is the foundation for workflows to automate text editing, web services, image manipulation, and more – all on an iPad, without needing a Mac. Editorial sits at the forefront of the post-PC era, and it’s become an indispensable tool for my professional life.

Editorial came out on August 15, 2013. Over the past nine months, I’ve seen Editorial go from a minor 1.0.1 release to a feature-packed, redesigned 1.1 that feels like a 2.0 update – the kind of deep, fundamentally different version of an app that several developers would charge for as a separate product on the App Store.

It’s undeniable that Zorn should have released an update with fixes and basic iOS 7 compatibility sooner, but it’s important to note that Editorial 1.0 (aside from minor issues) kept working well on iOS 7, and Zorn documented the development process with notes and screenshots on the app’s forums. As an Editorial user and reviewer, it’s been a long journey from version 1.0 in August 2013 to today’s 1.1 release, but it’s been worth it.

Editorial 1.1 brings a plethora of design changes, Markdown improvements, and automation breakthroughs that, just ahead of iOS 8, represent a major milestone for Markdown text editors and iOS automation. Editorial 1.1 may be a text editor on the surface, but, in reality, it’s a small revolution for iOS power users.

Read more


Editorial 1.1 Teaser

In post published yesterday on the Editorial forums, developer Ole Zorn shared more details on Editorial 1.1, announcing some features he’s been working on for the update, such as the ui module, which will allow users to create custom interfaces inside Editorial:

It’s not just a module, there’s also an integrated visual editor for setting things up without code, and in Editorial there’s also a way to build UIs around workflows, without having to write Python at all (though you can also mix and match). Before you get the wrong idea: This is in no way a complete wrapper around UIKit or some kind of Cocoa bridge, so you won’t be able to do a all the things you could do in a native app, but it provides a (hopefully) easy-to-use and pythonic way to create UIs that look and feel “at home” on iOS, and it’s possible do some relatively advanced stuff with custom drawing and touch handling.

For Editorial, I tend to think of this as a “plugin” interface that allows the creation of workflows that are nearly indistinguishable from native features. Obviously, this won’t be for everyone, and there will definitely be a learning curve, but given what I’ve seen this community come up with, I’m pretty confident that it will enable some people to really push the limits of iOS text automation (and others to reap the rewards via shared workflows).

I can’t stress this enough – the new module fundamentally reinvents the way you can build visual workflows in Editorial, and I can’t wait to share more about the workflows I’ve been working on.

Make sure to check out Ole’s post for screenshots of Editorial 1.1 on the iPad and iPhone.

Permalink

How To Open iCloud Tabs In Editorial for iPad

Editorial iCloud Tabs

Editorial iCloud Tabs

I’ve always wanted to be able to access my iCloud Tabs directly from Editorial, but, unfortunately, due to the lack of an iCloud Tabs API, that’s currently not possible. Last week, however, when I linked to the iCloudTabs for Alfred project by Kevin Marchand and saw that the workflow was based on a bit of Python code, I realized that I could modify his script to find a way to make Editorial read constantly-updated iCloud Tabs from a text file.

What follows is a combination of a server-side script and an Editorial workflow to read and open iCloud Tabs within the app. The system works and I’ve been using it every day for the past week with good results.

Read more


Matching URLs In Editorial with John Gruber’s Regex Pattern

Editorial for iPad

Editorial for iPad

When I’m writing in Editorial, I often need to make sure I’m dealing with a valid URL in the system clipboard, the document editor, or in a variable. To do so, I’ve long employed John Gruber’s liberal, accurate regex pattern for matching URLs, which has reliably allowed me to confirm that a workflow is about to handle a proper URL rather than a string of text that contains something else. Gruber recently improved the regex pattern again, and that seemed like a good opportunity to briefly detail how I’ve integrated his pattern in my workflows.

The key to match URLs and provide error-handling features in Editorial is to use a conditional block based on a regular expression pattern. Editorial comes with this functionality built-in: given a regex pattern, a block of actions can be run only if a value (plain text or variable) matches the pattern. In this way, you can run a set of actions if you have a URL, and another set if you don’t have a valid URL.

I’ve created a simple workflow that can be installed and reused as a preset in other workflows. The workflow, called Match and Open URL, consists of a single If block that checks for a URL contained in the clipboard. If you have a URL that matches Gruber’s pattern, the URL will be extracted from the clipboard and launched in the browser; if you don’t have a URL…it’s up to you to provide an alternative.

Editorial makes it extremely easy to build this kind of advanced workflow with just a few built-in actions. Gruber’s single-line version of the regex pattern can be pasted in Editorial’s If action with no modifications; inside the If block, the text in the clipboard is passed to a Find action that extracts a URL using the same, untouched single-line regex pattern. The extracted URL is opened in the browser and a HUD alert is displayed.

Combining Gruber’s regex pattern and Editorial’s workflow system can yield interesting results. You could use a variable instead of the system clipboard to match URLs; you could implement the pattern in a Repeat block that performs a set of actions for every matched URL found in the target text; instead of having my workflow inside an If block, you could match a URL among other bits of text, extract it, and do something with it. Editorial is a text automation playground and your imagination’s the limit.

You can download the workflow on Editorial Workflows’ website, and check out John Gruber’s regex pattern here.

Note: The screenshot above shows a beta version of Editorial, currently in testing.


Terminology Workflows For Editorial

Greg Pierce:

Terminology has always had great direct integration with our own apps, Drafts and Phraseology that allows you to easily lookup and select replacement words and have them directly replaced inline with your editing. You can see that integration in action.

In the latest version (3.0.6) of Terminology, I added a tweak to its URL schemes to allow it to integrate more easily with certain other apps, particularly Editorial, Ole Moritz’s excellent iPad text editor.

Terminology is my favorite dictionary app and I wish Editorial had a popover to replace Apple’s default dictionary, like Instapaper did. The workflows are the best alternative to that for now, and they work well.

It would be nice to have selectable synonyms and antonyms built into the system dictionary in iOS 8.

Permalink

Insert Markdown Image Links Interactively with Editorial

Stefan Wolfrum:

Because the markdown documents I write contain usually a few images from web sites I research (not from my iPad image library) and because Editorial includes its own web browser I asked myself: why can’t I just somehow insert a markdown image link in my document to an image that’s on the web page I see in Editorial’s browser? Either I’m missing something or it just isn’t there (yet). Well, because I’m always eager to learn I started to implement exactly that.

One of the most clever workflows I’ve seen in a while. I’m using a similar trick in my Feed Wrangler workflows, and Stefan’s idea can be easily repurposed for other scenarios. Well done.

Permalink

Simulating Multiple Cursors in Editorial

Editorial

Editorial

When I’m writing with Editorial or Byword, I miss the multiple cursors feature of Sublime Text. Seemingly an extra geeky addition with no practical utility, multiple cursors had become part of my editing workflow as they allowed me to select multiple positions in a document and act on them at once. For example, I could select multiple lines and prefix them with an asterisk to turn them into a Markdown list, or select multiple instances of a word and modify them with a single keystroke without using Find/Replace or other hacks. The feature was built into Sublime and it was great. So of course I made a workflow for Editorial.

Because it’s the end of the year and I’m feeling festive and thankful, I’m posting two workflows to simulate multiple cursors in Editorial. The first one allows you to save selections for multiple bits of non-contiguous text at once and, when you’re done, wrap them inside any character(s); it’s useful if you want to make multiple words bold/italic, or if you want to enclose them inside parentheses. The second workflow lets you add inline Markdown links for each selection, fetching a webpage URL from the Editorial browser. Read more


Getting App Prices with Editorial

Editorial workflow

Editorial workflow

When I write on my iPad mini, I often need to look up and reference price of apps that I already own. That’s a surprisingly hard thing to do on an iOS device, so I decided to remove the annoyance caused by this problem with an Editorial workflow. I call it “Get App Price”.

If you own an app, searching for it in the iOS 7 App Store won’t show you the price information alongside the app’s icon and description – you’ll only get an Open or Install button. Unlike the Mac App Store, there is no separate pricing field in the app information at the bottom of the screen, which usually forces me to go to a developer’s website to find out what the price of an app is.1 There wouldn’t be any problem if Apple allowed Safari to open iTunes web previews without redirecting them straight to the App Store, which is what they do on OS X. I have tried to force Safari to open web previews, and I even downloaded browsers that can set a modified user agent string to trick iOS into thinking they’re desktop web browsers worthy of a web preview – eventually, the App Store app always opened, displaying no price.

I set out to create a simple workflow to fetch an app’s title and price directly from iTunes with no clipboard import or other middleman. I later found out that you can tap on the “Related” tab in the App Store or gift an app to view its price, but I had already created a workflow that’s faster than opening the App Store and tapping a bunch of buttons just to get a price. I’m a free man, and I deserve my own App Store lookup solution.2

Read more