Jump to content
Storyist Forums

OneWordThenAnother

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About OneWordThenAnother

  • Rank
    Newbie

Recent Profile Visitors

49 profile views
  1. OneWordThenAnother

    PDF Support - Native View & Export

    Hi! Yeah, that's exactly what I was getting at. It's a feature that my old writing software had that I got used to, and I've recently been surprised at how much I relied on it. I often create "packets" to send out to readers at various stages that include the Title Page, Manuscript, and Summaries. I sometimes add a reference packet with Character and Location info. Right now, instead of two packets, I wind up with three PDF's for the first, and a dozen or more for the second! Having an Export to PDF option would make that much easier. Thanks for the tips on combining the files after export, as well. Acrobat has been my workaround in the past, but I wasn't actually aware that I could do it via Preview. That is a great stop-gap option for the time being, especially for those without access to Acrobat.
  2. OneWordThenAnother

    PDF Support - Native View & Export

    Hi Steve, Thanks so much for the reply. I am aware of the Print to PDF option, but I e found it to be limited as I mentioned above. Please correct me if I am wrong, which I may well be since I am a recent adopter, but what I've found is that Print to PDF only allows you to have one item per PDF (title page OR manuscript OR notes). What I was trying to say above was that having native PDF support in the Export window would allow you to choose which story parts get exported -- title page, manuscript, notes, AND summaries all to one file, for example, or just Character Bios and Location Info if you only needed a reference packet. With Print to PDF I've only been able to get it to do one thing per PDF file. Please let me know if I am missing something and there is a way way to get multiple story components into a single PDF file. Right now I wind up with one PDF for each required element from my side bar, and I have to 'print' them all individually, so I'd be thrilled to learn of an easier method. (I know this whole thing may sound like a silly nitpick, but when it comes to emailing, printing, uploading or FTP-ing to someone's server, it is significantly easier/less nerve wracking to be able to export a single, custom-tailored file for that usage than it is to try to correctly upload or email half a dozen component pieces.) Cheers!
  3. OneWordThenAnother

    PDF Support - Native View & Export

    I'm pretty new to Storyist, but unfortunately one of the very first things I noticed was its lack of PDF support. I'd love to be able to view PDFs natively inside of Storyist, as well as have the ability to export my manuscript to PDF once I've finished writing something. This is - to me - the most critical feature that is currently missing. -------- Justifications: Import: I do a lot of pre-writing and research using various other applications. I don't expect them all to play together nicely, so I've gotten in the habit of saving all of my research, character lists, background and designs, etc. as PDFs and simply importing them into my old workflow (Scrivener). They would all sit in my research folder on the sidebar, and then when I needed to reference something about my character I could pull up the PDF I'd created that had photos of style/outfits, background, and flow charts all in one document on my sidebar. Export: PDF is possibly the only document standard that literally anyone, anywhere in the world can open on any device. DOC/X used to have serious problems on iOS. PAGES is worse since it can't be opened on Windows. TXT loses the style, and others need specific apps. Even if you do manage to get it open, sometimes formatting is skewed. PDF opens on every OS - from mobile to desktops, Mac to Linux, and everything in between -- if for some reason your machine isn't able to by default, it's free to download a PDF viewer. It keeps all formatting between these systems without loss. If it were unintentionally edited or corrupted while emailing, etc. it doesn't matter and can't harm your original copy because it's a read only image file. (OS X can "Print to PDF" by default, and its a decent workaround for the time being, but it lacks the options of choosing what gets included that you get in export options.) Additionally, if you have Acrobat (which is incredibly cheap from Adobe Cloud now, unlike it used to be ) doing commenting and editing on a file using Acrobat is super fun and easy, and has the added benefits of 1) making it impossible to inadvertently leave a tracked change or comment in the document, and 2) forces you to go back into your own story to determine if the change is truly the best thing, or even if it needs to be more extensive, rather than simply hitting "accept". I started sending out PDFs by default years ago because of their ease of use. -------- So yes. Thanks for the awesome software, can has PDFS to make awesomer? (Post Script: When I originally emailed support about this, it was suggested that I bump this thread. There are a number of people in that thread requesting PDF support, but I decided to create a new thread because PDF export was not mentioned there, and I didn't want that request to get lost among the other comments. So please count their voices here as well!)
  4. OneWordThenAnother

    Storyist Sync with Aeon Timeline

    I would really love to see this too, but Aeon was written specifically for Scrivener. It started out as a small app before getting its own sub-forum at Lit&Lat, where users helped to define scope, and then it was built out to be integrated with Scrivener. That makes it very unlikely that full integration will happen, as it would require both developers working together (we can hope!). However, the file output by Aeon is really just xml, so Storyist could likely come up with a way to allow you to open Aeon files in Storyist and copy the data over. Here is a solution, though: It assumes that 1) you do all your planning in Aeon before writing (which I generally do, and tweak during writing) and 2) you own Aeon, Storyist, and Scrivener. You can create all of your timeline inside of Aeon just as you normally would. Then create a "Shell" project with Scrivener, and spend all the time you need getting your Aeon work synced up with its appropriate place in Scrivener. Then save the Scrivener file, and reopen it with Storyist. Most of the Scrivener stuff appears to get shoved in a pile the corner (because Storyist doesn't have customizable file icons, which I think are super useful), but it's all still there. In fact ALL of the Aeon Timeline items that have been synced remain intact in the sidebar, and in my testing they are all in the same place where I put them during the sync/subsequent tweaking. Then, all that's left is for you to copy/export this to the file you're writing in, or to write your story around the data you've imported! Bottom line: It's possible if you really love Aeon and need to use it for your work. I've done very limited testing with this, but it has worked for me. YMMV. Personally, I'd much rather have a pretty basic date/time flexible, multi-track timeline built into Storyist. I'm a huge, huge fan of having my story planning tools in the same software where I'm writing said story.
  5. OneWordThenAnother

    Comic book template page and panel auto numbering/renumbering

    I write comic scripts in addition to longer prose. I would be absolutely thrilled to see a comic book script template be added to the default set for BOTH desktop and iPad. It's one thing to create your own, or to use one that's been shared, but to have one that has been considered from the point of view of the software developer -- who really knows how things work and go together -- would be a huge benefit. Knowing that the comic template you're using has been thoroughly tested to not edit in its own errors that I might not catch (page numbers, an incorrect heading, etc.), and knowing that everything will still come out great on export would be a huge weight off. It's not just that its a hassle to create your own or borrow one from another user: its a bit nerve-wracking! PS: Scrivener has indicated that they have no desire to add a comic book script to their iOS version at outset (I can't recall if they've said they have any intention of correcting that after launch) and with ComXwriter also in a vaporware state Storyist would be the only iOS writing software with a native comic template to my knowledge. Definitely a nice selling point.
×