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.
Yes, N++ is sweet. I haven't used it a lot but I have done a little HTML in it along with a bit of Python in the Learn Python the Hard Way tutorial set. I would love to have a workflow setup but notepad++ is definitely a good text editor.
I bought Editorial just a couple days ago. Great app and I'm really looking forward to the new 1.1 version. One request, though. While the Dropbox integration is nice, is there any chance of including other sync services too, like Box or Copy? Thanks much.
Ole I think your are nearing the update Editorial v1.1. It's soon available on app-store I Think So. Best of luck & congrats...
Ole: Feature requests.
I have long file names and can't see full names in the side panel with 1.0 Notesy is the best at revealing full names in a single panel. Is it possible to widen the left panel to reveal more of the name? Or even make it full screen? Short of these changes, the ability to tap and hold to reveal the full name of the file or folder would be very useful.
Also would love a search feature ala Boxie and a back button that allows quick navigation through the folder structure, also ala Boxie.
Looking forward to 1.1!
Can’t wait Editorial updates for iOS 7. I’m going to buy it now!
Hope new version can remember the editor cursor point, so when the app switch out when IOS low memory,and then relaunch app can continue. just like Apple Pages.
We are waiting for a long time from 17 Oct 2013 to 22 Mar 2014 = (5 months, 5 days) = 156 days.
Please Update Soon...
Yay math! Can't rush perfection. I'm sure it'll be worth the wait.
The foundation settling is starting to show. It's been a year without nary a bug fix, not to mention an IOS 7 look and feel update, return TextExpander support, etc.
C'mon Ole, it's time to show your supporters that you support them back. Heck, I would even buy the product again or pay an IAP to get an update.
I must admit I'm getting slightly worried by the lack of news altogether. I don't mind developers taking their time to get things right but it's 6 months since Ole announced the 1.1 upgrade and we're no wiser as to the status. If snags have entered the process that's fine but I think it's good practise to keep your customers up to date on the situation not just those who are part of the beta development team.
I've invested an awfull lot of time into Editorial writing workflows that help me in my day to day tasks and it's by far my favourite text editor on IOS.
Please Ole at the very least provide your customers with a status update.
Via the Internet and all info being there, we know better TaskPaper integration is a real possibility, on the iPhone as well, and for that matter that an iPhone app exists (wether it will be released anytime soon or ever, I guess we can't officially know yet, but from things certain people have said, I think it's in progress - don't take my word for it). It's close I think, but unfortunately I'm not a tester :( so I'm speculating on observations. Granted, another official update on the site would be nice, but it seems like a complex app in comparison to many others, with a lot going into it. I know it's at least going to happen eventually, and I take the long time to mean it's going to be awesome and the relative lack of regular updates to mean he's too busy making it so. Maybe I'm just optimistic though.
If you look at Ole's twitter, you get the occasional nugget, like this screenshot of the iPhone app. From all indications, this sounds like a very significant feature update that also adds a new app (iPhone). Understandable that it takes a while to dev and polish.
jonmoore, I'm with you 100%— we need communication, on a regular and consistent basis, if we're going to have a level of comfort that the product is moving forward and is actually on the horizon.
That was my whole point. I'm fed up spending time and effort with products (such as i.e. the aforementioned TaskPaper) only to find out they become unsupported on my platform of choice (IOS) and end up in the far flung reaches of the App store with the tumbleweed. I've bought and supported all of Jesse Grosjean's programs and continue to beta test the latest version of FoldingText but when you build personal workflows around specific software and find that the developers are unable to support their creations it's a major hastle.
It's not a problem if a development strategy changes as appears to be the case here with Editorial (with what appears to be an integration of Jesse's TaskPaper syntax within Editorial and I'm sure many other changes) but leaving customers in the dark with no explanation is not good quality customer relations. To announce a product upgrade in October and then only seed snippets of update info to a Twitter feed for the next six months is not what I think of as good practise. I work in the software development business too so I understand the complications that can happen but they should never get in the way of clear & open communications with the customer base.
Apologies if any of this sounds harsh, especially considering the innovative products Ole has brought to market over the last few years but running a successful company needs exemplary communication skills as well as superhuman programing chops.
@pruppert I've been excited since I first saw the screenshot. It's shaping up nicely it looks.
As for updates, like they said, you follow the twitter account and you get updates on occasion. Traditionally there's a twitter account specifically for the app or the dev company where updates can be found, but that's not the case here. I'm anticipating it and I'm generally impatient, and I also understand the desire for more info concerning the progress, when you invest your time in it. But considering how a lot (I mean A LOT, but not a majority) of devs respond to requests for progress updates, he handles it quite well.. I see him answer people, even if he doesn't seem to get on there often. I've seen many devs who get offended or downright irate about a simple "are you able to give an eta?" And that may be because they're asked a lot, but I think it's a bit ridiculous. At least Ole is polite as can be about it all.
@Ole Thanks for the iPhone support. Looks awesome in screenshot we are waiting for that take your own time to complete the project perfectly done.
@olemoritz @LeninRzSz and talking of the 1.1 update that was announced 6 months ago... Any new status update?
@LeftsideWobble @LeninRzSz I know, I'm sorry. Hope to have some news soon. :/
3:54pm - 10 Apr 14
@due3die I second that. Would I love to have it now? Absolutely! But I'm fine with waiting if that means it is the best it can be. Take your time and do it right, which I've no doubts you will.
I may be mistaken, but I thought the notion of waterfall development had gone the way of the Dodo and we were living in the sparkling new world of agile?
Take the time to do things right, sure, but when there is more than a year without a bug fix, I have to wonder if there isn't something seriously wrong. Heck, even Pythonista had an IOS 7 refresh...
On "the 1.1 update that was announced 6 months ago" I would say it WASN'T announced but rather a "keep the faith" teaser. But people take such things as an announcement.
I would say, with no grumpiness whatsoever, it'd be better to have a series of small(er) updates rather than the one very big one we're now all eagerly anticipating.
It's a matter of "news management" and I hope Ole's learnt something from this.
But this all smells of a "sole developer" situation where the product plan is vulnerable to lots more things than if a big corporate were attempting to push it out. But then I can't imagine Editorial (or Pythonista) ever getting past the Product Planning stage. (At least not in MY big corporation.) :-)