If it's not essential to everyday writing, it doesn't belong in the application. You should be able to dictate the way you want to work (I hate software that tries to force you into a particular work flow), so it has to be flexible.It should provide for easy cross-referencing, both with other text documents and media files used for research.You should be able to get everything out of the way if you want to so that you are left with just you and your text.Every document should be linked with a synopsis, to facilitate easy outlining.It has to allow fluid movement between outlining, composing and editing.
#MACJOURNAL FONT TOO SMAL MANUAL#
If you need to glance at a manual before you start writing, something is wrong. These have been my objectives in designing the interface: Getting the interface right has probably been the single-most difficult aspect of designing Scrivener - after all, a good interface is crucial, and can make or break an application. This is really the third iteration of Scrivener's interface the fourth, if you count Hemingway, my prototype for Scrivener. (Pretty much all of the code for Scrivener has already been written - the hard part now is just putting it all back together so that it works well in the new interface, optimising it and ironing out any glaring bugs - a couple of months' work at least.)
I had it sketched out on paper, but I wanted to see what it would look like in practice: there's no point in forging ahead unless it looks like it's going to work. Whilst I've been doing this, I've also been mocking up the new interface for Scrivener.
I'm currently finishing off the Literature & Latte website: getting the new forum up and running, gathering together free downloadable stuff (a couple of trivial programs and some classes for Cocoa programmers), putting together a links page, and of course getting the Scrivener page ready (so that I'm ready to hit the ground running when it is actually finished).
0 kommentar(er)
