First Look at Editorial 1.1
As you might imagine, I'm quite busy updating Editorial for iOS 7. I still have a lot of work ahead of me, and I can't give you a release date yet, but I'm getting closer, so here are a few details. First things first – screenshots (click on the previews for full-resolution images):
(obviously, these are work in progress, the final version might look a bit different)
Editorial 1.1 will require iOS 7. I know that some of you won't like this, but sooner or later, it's inevitable, and all iPad models that run iOS 6 also support iOS 7, so this doesn't mean leaving any older devices behind. iOS 7 is so different from its predecessor that it's a lot more difficult to support older versions than it was with previous upgrades.
The update will include a complete UI overhaul, some new features, and bugfixes. Here's just a list of the most important things:
- Live word count (optional, you can see how it looks in the first screenshot)
- Possibility to create shareable links for Dropbox documents
- New workflow action to do in-document search
- New workflow action to add URLs to Safari's Reading List
- New text-to-speech workflow action
- Courier Prime as a new font option
- Options for disabling extended Markdown syntax (e.g. footnotes), these options will also be available in the Convert Markdown to HTML workflow action
- Customizable HTML template for the Markdown preview
- Option to disable the snippet expansion sound effect
webbrowser.can_open()function that can be used to determine programmatically, whether other apps (that have URL schemes) are installed
- Snippets will no longer be inserted twice when tapping the suggestion bubbles
- TextExpander integration will be supported on iOS 7
- Headings will no longer require a space after the '#' character to show up correctly in the HTML preview (this is currently inconsistent between the in-editor preview and the HTML preview panel)
As I said, it's not done yet, and it's always difficult to estimate release dates, but I still wanted to give you a little preview of what's next for Editorial.
Thumbs up Ole — looks nice!
Looks already promising. Are you going to resolve the display problems when using bluetooth keyboards?
@KU Yes, I expect this to be fixed with the update. iOS 7 has improved support for extra keyboard rows etc., so I could just remove a bunch of drawing code that I suspect was responsible for the flickering.
Came here because I saw that Text Expander was broken currently (in iOS7)... so really glad to hear it's on the fix list!
One feature I've always wanted on iOS in any text editor, would be the ability to have two text documents open side by side or stacked (depending on iPad orientation, and need for width or height... so configurable would be nice!). That would give iOS a huge bridge towards OSX level of productivity for writers, coders, etc. Would something like this be possible to add to Editorial, especially now with iOS7?
I've seen a couple apps try to pull something like that off, but poorly implemented. The browser/editor is an excellent step, but two documents is the key. Even if one of them had to be read-only, it would be a big help. I'm always doing research and then writing based on that research. Flipping between documents or apps just isn't efficient. It's like the #1 productivity killer for me with the iPad.
Looks like a really great app!
@Ole We are waiting for Editorial 1.1
Not me, I haven't explored a fraction of 1.0 yet.
Sounds great, I'm looking forward to seeing it live on my iPad.
What about switching the markdown engine to "real" MultiMarkdown instead of sundown? I believe this would be very helpful, even though I ignore how hard this would be to implement...
This is a wonderful and immensely useful app. I have a suggestion/request for the next version.
Could you support displaying equations via Mathjax in the HTML preview? I am aware that there is a workflow for this. But this workflow depends on the Mathjax CDN and hence will not work offline. It should not be difficult to have the minimal Mathjax files right within the app. Since the WebKit browser used in the HTML preview supports SVG output from Mathjax (and SVG output is also faster), the memory requirements to have the Mathjax folders right within Editorial will also be very minimal if SVG output alone is configured.
Please @omz Can't wait. Please update as-soon-as.
@omz super excited. The screenshots look pretty great. Excited to check out the new features. New to Editorial still, and newer to python, so hopefully this isn't a dumb question. Could the webbrowser.can_open() function be used to determine which apps on that device have url schemes, in a way that it could pull a list or even tell you directly the schemes, or is it simply for the script's benefit? Hopefully I managed to ask what I meant. Keep working on this amazing software, and I'll keep using it. Thanks for your time and effort, cant wait!
@the_buch It's unfortunately not possible to get a list of all supported URL schemes on a device (there's just no API for that), so you'd have to check a list of known ones to see which apps are installed...
Okay. That makes sense. Thanks for the swift response! Have a nice day
Sorry for asking this question again (but it was not resolved): Would the new version use a "real" MultiMarkdown engine? For people using subscript frequently (as in H~2O or H_2O for water) this is really impornant.
Thanks for your feedback and best regards!
Any updates for when Editorial 1.1 will be completed and released?
I would also love to see an iPhone and Mac version as well.
I've really been enjoying Editorial. Fantastic work as a whole and the 1.1 update is promising.
My workflow list is getting long and cumbersome. Are you considering adding the ability to organize workflows in a hierarchical structure of some kind like user-customizable folders or a similar function?
I would be interested in the workflow organization feature suggested above, by mconnors as well. The list is growing at least a few times a week it seems. Of course, even without such a feature, I'm still just impressed with the fact that this exists at all.
I second the comment about having mathjax local. Most of the time I don't have wifi access on my iPad. I need to have notes with math and every other app falls short. This app would be perfect with local mathjax.
I tried to have a local MathJax folder in my dropbox. And it works after adding the mathjax <script>...</script> element in the markdown file with the link pointing to the local Mathjax folder.
However, markdown seems to be parsing before mathjax gets control. Though a lot of the equations get parsed by mathjax, anything with a superscript is parsed by the markdown parser. Hence some of the equations look ugly.
There might be other elements (in addition to superscript) where parsing fails.
It should be possible to take care of this and also include a <script>...</script> to the local mathjax folder in the template used to render the HTML preview.
Hoping this will appear in version 1.1 (which we are awaiting eagerly)