![]() ![]() Folder and text file look, in Storyist, like chapters and scenes in WriteWay and Scrivener. In both Scrivener and WriteWay, Chapters were on one hierarchical level in the equivalent to the 'Project' view, the scenes on a subordinate level under their chapter. In Scrivener they were folders, in WriteWay they looked and acted like folders. Not because there were underlying file structure reasons, just because that looked familiar. Let me keep this simple, for me, so I don't get lost in the complications.įirst: Write or wrong, after 3 years of WriteWay and 6 months of Scrivener, my instinct was to use a folder for each chapter, a text file for each scene. I don't know why this is so hard for me to get my head around. This does seem to be a bit of a stumbling block for people coming from Scrivener (which doesn't support styles), and the ability to merge files and their associated style sheets is something I'd like to add to Storyist to ease the transition. You don't need a separate step to just see the manuscript.It doesn't impose an extra level of mental overhead to remember that a file is actually a scene and a folder is actually a chapter title.It is easier to import from or export to conventional word processors.It is easy to apply consistent formatting using the stylesheet.Using styles rather than a folder structure to specify hierarchy in your manuscript has a couple of benefits: You can still keep notes/index cards on a per chapter or scene basis and you can still rearrange the chapters and scenes within the manuscript by dragging the outline items in the Project view or by dragging the cards in the storyboard view. The difference from your previous workflows is that this separation is usually accomplished in Storyist using heading-level styles and not by creating separate files. This is actually how the templates are set up. I want my document separated into chapters and scenes in Storyist. With the vertical editor split writing from the outline is a piece of cake. One of the big features of programs like Storyist, Scrivener, and WriteWay, is being able to see, organize, and manipulate the document as chapters and scenes, and have character and research data readily available in the same on-screen environment. If I was going to write the whole novel as one file, I'd just use WORD with the chapters as outline headings. In Scrivener it's harder, one has to use the split feature. ![]() WriteWay would import and split the WORD file into chapters and scenes. It can't, but Steve has indicated it's on his list of features to implement. From Scrivener it was a bit of a mess, but from WriteWay it was complete, chapter numbered, and properly formatted. In both WriteWay and Scrivener I was able to export (compile in the case of Scrivener) the entire novel as one large RTF or MS-WORD file (both worked just fine). I worked that way in Scrivener and WriteWay. I gave some basic instructions in that other thread. The easiest way to do that is to merge the files in Scrivener, then reimport (once) into Storyist as a single document and work from there. So he has to get them into a single file before he can export them. Fitch imported his file from Scrivener, where it was (unbeknownst to him, I'm guessing) stored as a zillion separate files, all of which are now revealed to be separate documents. See my comment in the Styles thread: it's easy as pie to move an entire formatted novel from Storyist to Word, so long as you are writing the novel as a single Storyist document. I came to Storyist from Microsoft Word, and very much liked the way Storyist encouraged me to work. And you never know, you might try experimenting with other workflows and prefer them for future novels. That's great! But it's not "wrong" to do things another way, any more than it's "wrong" to do things the way you do. And it sounds like you use a workflow that Steve is aware of, and will accommodate with future development. You're new to Storyist, and have a different workflow. For many users familiar with Storyist, this is our workflow. And then you can print and export the whole novel as one document. The Project View then allows you to treat each chapter separately almost as if it were an actual separate file: move them around and reorganize them, the page numbering will change automatically, and so on. When you create a Storyist manuscript, you can use Chapter Styles to create your chapters in the manuscript. I don't think there's a right or wrong, it's all a matter of workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |