Jump to content
Storyist Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About pbridges

  • Rank
  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 navigatio
  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 r
  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/
  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 n
  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
  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. I
  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
  • Create New...