This one is mostly a bugfix and usability release. Enjoy.
All posts by Mark
A Shameless Appeal For Reviews
If you’ve used StoryBox at all, whether you own it or not, I’d like to ask you a favor, especially if you have a blog or some other public forum.
Could you please post a review of StoryBox? Tell people what you really think. Be honest about it. If you loved it, tell people. If you hated it, tell them why. Tell me why.
Post a link in the comments here once your review is live, or send me the link at
support@storyboxsoftware.com and I will repost it, as well as link to it from the StoryBox website.
I’d really appreciate it.
And if you haven’t tried StoryBox, download it and try it and tell me what you think.
StoryBox 1.3.103 Released
Yeah, it’s the day after a release and I’m releasing another one. Got some good reports yesterday of some formatting troubles with certain things in the ePub export, and I just couldn’t stand to let them sit there and fester. All of them are fairly minor, unless you’re trying to have the copyright symbol display correctly, or you use accented characters.
Read the release notes. There’s information about how to add clickable URL’s and email address to your ebook.
StoryBox 1.3.102 Released
Today’s release marks the release of an essentially complete epub export. You can add cover and scene separator pictures. It changes the straight quotes to curly. There’s also a few bug fixes along for the ride.
Check out this link for a quick tutorial on making epub’s with StoryBox
Making Epub and Mobi files with StoryBox
What? What? Really?
Yes. Here’s the rough and tumble guide to turning your StoryBox project into epub and mobi files. First, you have to have StoryBox installed, and you have to have your novel or short story written or imported into it. If you’ve never used StoryBox before, read the help sections on importing, and you should be able to get your project into StoryBox pretty quickly.
Once your story or novel is ready to go, you need to add the cover.
First, you’ll want to make sure you have your cover image in a proper format. Using MS paint, or other image editing tool, create a cover, then save it as a “jpg” image. You should size the image so that it’s not terribly large. I like 500×750 pixels, but if you find someone recommending a different size, use that if you wish. You just need to make sure it’s sized appropriately before you import it into StoryBox.
Next, Right click on the story node in the File Drawer and select “New Picture”. You can actually put the picture anywhere in the tree you want, I just like them as children of the story. Find the cover image you saved, and click Open. Once it’s done importing, you want to click on the image document in the File Drawer to open it, and then click the “Cover” checkbox in the Properties panel.
If you wish to use a picture as a scene separator, you can import another picture (I recommend using a png since they can have transparent parts) just like you did the cover, then click the “Scene Separator” box in the Properties panel.
Now, select Export from the Project menu. A small Export dialog will appear. Select “EPUB” from the File Format dropdown. If you want to use the picture for the scene separator, you will need to select “[picture]” from the Scene Separator dropdown. Click Export, choose where you want to save the file, give it a name and click save, and you’re done with the epub export.
To make a mobi file, download Calibre, a free e-book converter. Start it up, drag the epub file into it, right click on the file and select Convert Books->Convert Individually. A dialog opens up with a bunch of options. In the upper right corner, there’s a dropdown labeled Output format. Select MOBI from it. Click OK, and it starts converting. When it’s done, right click the book in the list again, and select “Open Containing Folder”, and it will take you right to where the .mobi file is. You’re done. In my tests, the conversion is pretty dang good and worked on my wife’s Kindle flawlessly.
Here are a couple tricks. If you want bold chapter titles, go into each chapter document, select the text (which defaults to “Chapter [chnum]”) and make it bold by hitting Ctrl-B.
The Table of Contents names are derived from the names of the documents in the File Drawer. Make sure these are how you want them. You can make the chapter titles in the actual document match the Table of Contents by using “[doctitle]” in the text in place of “Chapter [chnum]”.
If the paragraph indent is too large, this can be adjusted by changing the over-all paragraph indent in Preferences-Format tab. Paragraph and line spacing is ignored because on some readers, they don’t handle paragraph spacing well.
If you need to add some extra line breaks, you can put [br]
where you need them. Places where you might want to do this are on the copyright page or an acknowledgements page. (Edit: I’ve changed the tag. Using html tags no longer works at all for a couple important reasons, one of which is to allow you to use > and < in your text).
If you need different license pages for different distributors, remember that you can use the “Include In Manuscript” checkbox on the Properties for each document to specify which documents to include in the export.
My goal for epub generation is NOT flexibility in format. My goal is having it be quick and simple to generate a professional looking epub file. Let me know if you think of an easier way to do something.
StoryBox 1.3.101 Released
This release fixes a crashing bug with the outline view when scrolling.
When I released the last version, the component vendor that provides many of the controls I use (including the grid used in the outline view) had released an update that fixed some minor issues and promised performance improvements. So, I updated StoryBox with that updated version.
Unfortunately, they introduced a bug in the new version that created the unhandled exception message that people were seeing when I tried to restore the expansion state of the outline.
So, in this version, I’ve rolled back to the previous version of the components. They say there will be a fix for it in mid March, at which point, I’ll update StoryBox to use the new version. That new version should have a fix for another major issue, as well.
What’s really annoying is that figuring out what was causing this problem basically caused me to lose two days of writing time.