(The title of this post literally has no relevance except that it has "Lion" in the title.)
I have recently mentioned that Scrivener 2.0 features the ability to sync documents with Simplenote for the iPad and iPhone, and also that PlainText for the iPad works with Scrivener 2.0's new folder-syncing feature. Additionally, Notebooks for the iPad by Alfons Schmid works very well with Scrivener 2.0's new syncing features too. David has just finished putting together a video showing Scrivener 2.0's folder syncing feature in action, using PlainText and Notebooks as examples (although it also shows how you can use the feature to share documents with Word):
Jesse from Hog Bay Software (who created WriteRoom and TaskPaper) informs me that PlainText for the iPad and iPhone is now available (for free) from the app store:
David has posted a sneak-peek preview of Scrivener 2.0's syncing with Simplenote for the iPad:
In among all the excitement of getting Scrivener 2.0 ready for release (which, to remind you, will be out in late October, just in time for NaNoWriMo), we have another rather large announcement which we've been keeping under wraps for the past couple of years:
In my last blog post, I talked about all the things that weren’t coming in Scrivener 2.0. Now it’s time to talk about some of the goodies that are coming. Right upfront I ought to say that the focus has been very much on improving Scrivener’s existing feature-set by better integrating various aspects of the interface and making Scrivener easier and more pleasurable to use in general. I always think very carefully before adding new features - it’s impossible to please everybody because every user has something different on his or her wish list, and if you try you just end up with software that is bloated and difficult to use. So, I make no apology for concentrating on the core features rather than trying to shoehorn in features I don’t think belong. And yes, that’s my way of saying that you won’t find anything particularly whizz-bang in this list - but you should see a solid set of features that you will find useful in the endeavour for which Scrivener was designed: writing.
Earlier this week I completed the last major block of code for Scrivener 2.0 - at last. Now all that remains is a number of small issues and tweaks and then two months of beta-testing and bug-fixing before the release in October (barring any major catastrophes or problems that crop up during beta-testing).
This morning someone asked me how big Scrivener’s code base is, and I didn’t know how to answer - yet it’s something I’ve been wondering myself. It comes up occasionally, usually in two situations: 1) Someone writes to me wanting to know how much code it took to create Scrivener, because they have an idea for a program and wonder what’s involved; 2) Someone is insisting that I could port Scrivener to platform X or “just add” Y “easily enough” and is getting uppity that I’ve said no, so I want to puff out my chest and huff, “Look, I have written six billion lines of code mostly unique to the Mac platform and I’ve already got grey in my hair - coding Scrivener ain’t like dusting crops, kid!” (These exchanges usually end with me apologising for something.)