Jump to content
Storyist Forums

pbridges

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About pbridges

  • Rank
    Member
  1. Okay, I'll keep using the nested way for now. It all ends up the same on the page, but requires a little more work in navigating. But it would definitely be a great feature to add in an update, and would put Storyist ahead of the curve for screenwriters. It would allow customisation of workflow where all other programs dictate a workflow. And that seems to be most screenwriters' issue with the major programs. To go even further, it would be ideal to have an option to exclude/turn off an Outline element from the page as well, so you could have Act, Sequence and Scene cards for navigation and notes in Outline/Cards, but they would not appear on the document itself. This would be great for those who don't like a cluttered page, but would also be invaluable for printing/exporting different documents from the one file. For example: exclude Act, Sequence and Scene elements from the document, and your screenplay is ready to print/export as a finished screenplay. But turn them back on and then exclude/turn off Scene Headings, and the document is now a more traditional Outline ready to print/export. Feel free to move this to the Feature Request section. Thanks.
  2. Just for reference sake, here's what I'm trying to achieve in pictures... OUTLINE & SCRIPT INDEX CARDS & SCRIPT When it came time to export to FDX, I would just duplicate the document and delete everything except the yellow cards, giving me the final Screenplay view, properly formatted.
  3. Yeah, that's what I've been using so far, but it kinda makes a mess of the Index Card view when you nest/tier these elements. What I'm more looking at is whether it's possible to force a BodyText style to be recognised as an Outline/Project element, the same way that Scene Heading is. All of the Screenplay elements are BodyText, but Storyist makes Scene Heading an element that shows up in the Outline/Project views. What is it about Scene Heading that makes it an Outline/Project element, as opposed to Action, Character, Dialogue; which are also BodyText but not markers? I only really want to use Acts and Sequences as superficial markers in my documents, and my thought was that I could duplicate the Scene Heading style and make new Scene Heading-like elements called Act and Sequence that would show up in Project/Outline. They would behave exactly like Scene Headings as far as the Outline and Document are concerned, but they would have their own styles for visual reference. I tried making Scene Heading a Heading 1 element, then duplicated it and made Act and Sequence also Heading 1 elements, but then the Outline and Index Card view adds sub-documents for every Act, Sequence, Scene and Scene Heading. Is there any way I can duplicate Scene Headings, name them Act, Sequence and Scene, and have them behave exactly like a Scene Heading, including being added to Project/Outline?
  4. When working on screenplays, I like to use Acts and Sequences -- but I don't really care if they're nested or not. As long as I have a visual marker on the Outline for organizational purposes, I'm fine. On the Screenplay template, Scene Headings are automatically added as Outline elements in both the Outline and Project views. Is there any way to create a new style from the 'Scene Heading' style and have it also be an object that shows up in the Outline? For example, I create new styles called 'Act' and 'Sequence' from the 'Scene Heading' style, and each is a different text color/bold/underlined etc. as a clear visual marker in the document, while also being an element/style that creates a new card/section in the Outline and Project view. That way, ACT I and Sequence Name are displayed in the document, and its corresponding card/section can be navigated and edited with Act synopsis and Sequence synopsis. Then when it comes time to export to FDX, I can just remove/omit the Act and Sequence cards so that only Scene Heading elements are present in the presentation/reading draft. ACT I Race Sequence EXT. RACETRACK - DAY This is the scene description. INT. RACE CAR - DAY This is the scene description. Heist Sequence EXT. BANK - DAY This is the scene description. ACT II etc.
  5. ...and it sucks. I can't believe they took two years to develop something with so few features. No index cards, no scene navigator... Storyist is still the best FDX editing software for the iPad, but please please please add a software TAB key for the screenplay editing view. It's all it needs. Everything else is just right. Please just add a TAB key. Please?
  6. An option to highlight (changing the selected text's background color or even just changing the color of the text itself) is helpful, especially for people using FDX files. Final Draft has this feature, and it's almost essential for anyone working with another writer or an editor. The editor or co-writer can skim through the script and look for changes you've highlighted. I know Storyist supports FD 'notes', but highlighting goes hand-in-hand with that feature for writers/editors. When working in FD, you highlight the section of text you're referring to and then add a note to it if necessary. I'm not sure if iOS allows selected background color changes in this way that would support true highlighting. If not, it would be great if Storyist could interpret highlighting from FDX files and convert them to colored text, bolding, highlighting or something else that distinguishes FDX highlights from the rest of the document.
  7. Yeah, I would probably +1 this as well. I've never had the iPad lose a file yet, but a simple 'sync save' button on the document you're currently working on would ease a lot of concerns. Even if it's only a background shortcut that syncs your entire Storyist folder the same way it does when you're on your Documents screen in the app. Doesn't need to just sync the one document you're working on if that's too complicated. Would just be simpler than exiting your document to sync at the documents screen...
  8. I'd like to add my vote (or desperate pleading) for an iPhone app. And think of it this way; when Final Draft launches their Writer app, it's going to be iPad-only. Storyist could have the advantage of being the screenwriting app that opens and edits FDX files on all platforms (Desktop, iPad and iPhone). Storyist is the only iOS writing app that comes anywhere near being as functional as Final Draft. Heck, if you allowed the highlighting function from FD to work.display in Storyist, I would gladly discard FD all together.
  9. One of the other iPad writing apps has this, and it is its sole redeeming feature. They have it as a paste-up button above the keyboard. Writers who work on desktops or laptops with the major writing programs are used to the 'hit Tab' to progress workflow. You start writing INT. or EXT., the program automatically knows this a scene and formats it in CAPS as such. Hit enter and you're straight into action description. Hit enter again and you've got another paragraph of description. But if you hit Tab instead, the program knows to go immediately to Character Name. Hit enter and you're in Dialogue. But hit Tab instead to write a Parenthetical. Hit enter and you're in Action again, unless you start typing INT. or EXT., then the program knows you're on a new scene. Rinse and repeat. I know you can select what category your current typing falls into, but don't underestimate the almighty Tab as a quick and intuitive drafting tool.
  10. If you want this to be a solid competitor for the eventual FD and MMS apps, then here's what you need to consider: Slim it down and implement it as a logical and progressive workflow that covers the entire spectrum of writing. Screenwriters work in stages. Notes/Brainstorming > Index Cards > Outline > Draft. The character sheets and scene sheets etc. are great, but working writers want something that is intuitive. Like a note/brainstorming idea you've had? Allow it to be 'pushed' to an index card, so the writer can go into the Index Cards and refine it as a scene. Index Cards and Outlines are different to different writers. Some writers use their Index Cards to reference when writing a proper Outline. Some writers hate writing Outlines and just paste up their Index Cards as the Outline. But a good Outlining feature can work in both interpretations. Sophocles was a great abandoned writing software that the majors are now referencing for its intuitive Outline building features. ACT >SEQUENCE >>SCENE >>>BEAT Like the scene you've built as an Index Card? Allow it to be pushed to the Outline, where it can either be left as is, or written into a more prose form of Outline, depending on your preference. The flow begins in Notes. Fill it with everything in your head. Push what you like to Index Cards for the next stage, because all of your other notes are still going to be there in 'Notes' if you have to come back to them. Refine your ideas in Index Cards. Push what you like to the Outline as a Sequence, Scene, Beat etc. The scenes that didn't make the cut for your Outline are still going to be there in 'Index Cards' if you want to add them later. You build your final Outline the way you want. Organise your Scenes and Beats into the appropriate Act and Sequence so that you have a linear overview of your story, clearly segmented. Your final Outline is what you write off. Offer the option to present it as a traditional outline, a basic scene summary or just as finalised Index Cards. Then the writer can work side-by-side in Draft mode. Allow it to be collapsed/expanded for quick navigation purposes. Presto! A screenwriting app that finally works how most writers do. I like Storyist. The other Screenwriting apps are useless, because they don't actually present things in the logical order that a writer works. 'Pushing' things from one stage to another would be a valuable feature. Keep the Character, Scene sheets etc. Have them as folders in Notes. But you really need to seperate and compartmentalise all of your product features into the clear steps of the writing process: Notes > Index Cards > Outline > Draft. Having them as a mess of folders is like having everything strewn all over your desk. These ideas of defining the steps of writing would serve well in both your Desktop and iPad apps. Keep it simple and linear and writers will love you for it.
  11. You're confusing Index Cards with a Scene List. Index Cards are for summaries and notes, and I don't know any working pros who use them in the way suggested for change. By all means, offer a toggle between summary/note Index Cards and cards as a Scene List, but do not get rid of the first option to appease the second. You would be better served (and create much less confusion) by having Index Cards be purely for their traditional purpose of summary and notes, and implement a Scene List with collapsed/exploded view. Then users can decide whether they want their true Index Cards for reference beside their script, or a navigable Scene List.
×
×
  • Create New...