Thus you could outline in advance and use the synopses as a reminder about what to write, or write like mad to begin with and then get an overview afterwards for redrafting.ģ) The ability to review research files such as images, PDF files and other chapters or notes alongside your text, in the same window. You should be able to structure these chunks however you want.Ģ) The ability to associate a synopsis with each chunk of text that could appear alongside the document (or chunk) while working on it, or in the context of other synopses so that you could get an overview of the whole (the latter was implemented as the major feature of the corkboard and outliner). I’ve said this elsewhere, but as it’s relevant to what I want to cover in this post, I’ll recap: the three main features I ended up coding Scrivener for, were:ġ) The ability to work on a long text in smaller chunks, and to have these chunks combined upon export (and in the event, I also added dynamic combination for editing - Edit Scrivenings). I know this, because if it had been done before then I wouldn’t have spent months learning how to code and then two years putting Scrivener together I would have just used one of the other programs out there and got on with writing (or more honestly, I would have found a different way of procrastinating). I designed Scrivener 1.0 in isolation as a tool that would suit my own needs for writing long projects, and while I can’t claim that many of its individual features were particularly unique (although some were), it combined these features in ways that hadn’t been done before. This is down, in large part, of course, to the users of Scrivener 1.x, for their feedback and suggestions and the years of real-world use Scrivener has now had. It’s still the Scrivener you know (and hopefully love), but refined and with all its features much better integrated. It’s been worth it, though - I’m pompously proud of Scrivener 2.0. It’s been so long since I first mentioned that I was working on Scrivener 2.0 that I’m sure there are those who think it’s vapourware, and I can’t blame them it has been a long, hard slog and I sometimes thought I’d never reach the end, but the finish line is now in sight. The best way of becoming a beta-tester in the future is just to be really helpful if you find any bugs and to be active on the forums with helping others.) ![]() (A note on beta-testing by the way - thanks for all the volunteers but I now have more beta-testers than I know what to do with, so I can’t accept any more at the moment, sorry. ![]() 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). ![]() Earlier this week I completed the last major block of code for Scrivener 2.0 - at last.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |