Storyline --> iBooks Author = problems

Jul 16, 2012

Hi all -

First, I have to say that I'm absolutely loving using Storyline. It's a blast.

I specifically got Storyline because I wanted an easy way to generate interactive HTML5 for use in Apple's iBook Author program to make interactive widgets for my eBooks.

So I decided to start very small and make something very simple to just test things out.

The good news is that I am able to publish a simple storyline project to HTML5 and convert it to a widget for inclusion in iBooks Author (I have to remove the .SWFs  and .GIFs and include in info.plist - but after that, it imports with no problem).

And then, within iBooks Author, I can test the widget out and it works EXACTLY as I would expect. Very cool indeed.

The problem occurs when I publish the book to the iPad. Evidently, Storyline generates some code that checks if the  project is running on iOS, because I when I tap the widget, I am transported to a screen that has a blue play button and a missing graphic (which should be the thumbnail.jpg of my course).

So my first question for you is this: what can I do to avoid the check for iOS so that I don't see this intermediary screen.

But there is one additional problem as well. After tapping on the blue play button on the above mentioned screen, I go to a screen that presents my course - but not well.

The problem here is two-fold. First, the course is positioned too low on the screen and its border is cut off. Second, the active tap areas do not correspond to the individual graphics that have the triggers placed on them in Storyline - everything seems to be shifted down and to the right by a good 200 pixels or so. And again, what's odd about this is that it plays fine in the simulated environment in iBooks Author and fine in a browser as well.

The above described behavior occurs regardless of what size I make the Storyline project (I've tried several) and regardless of what Browser Settings I use in the "Player Properties" tab in Storyline (e.g., Resize Browser to Optimal Size, Display at user's current browser size, etc. I've tried them all).

So given what I'm trying to do, my next questions to you are this:
- Is there a way I can control how far down the course is positioned?
- Is there a way I can control the size of the displayed course?
- What can I do to make the triggers realign with the graphics?

I'd be very grateful if you could try to help figure out how to get this all working. Until then, I'm not going to be able to use Storyline like I had hoped.

Thanks so much.

Joel Epstein

7 Replies
Joel Epstein

Bill -

Thanks for the reply.

Unfortunately, I get the same behavior whether I specify the "story.html" or the "story_html5.html" in my info plist.

The screwy thing is that when I preview the widget in the iBooks Author environment on the mac, everything plays just fine.

But when I actually load my book onto the iPad,when I tap on the widget, I get an intermediary screen that displays this blue button and a missing graphic (which should be my thumbnail.jpg - but for some reason it isn't being read). When I tap on the play button, my StoryLine course does launch, but it's displayed too far down on the screen and the touch-spots don't align with the triggered graphics.

Any clue as to what I can try next?

I'd appreciate any advice you might have.

Peace.

Joel

Joel Epstein

Thanks for the suggestion. Unfortunately, this is not a cache issue because it happens with all StoryLine courses. The problem is that the code SL produces contains some iOS checks and handles things differently if the course is being viewed on an iPad. I need to find a way around those checks.

Any ideas?

Peace.

Joel

Joel Epstein

Actually, the tech support folks at Articulate eventually just told me that using Storyline in this way was not supported. I've moved on to HyperStudio - although they don't have native export for iBooks Author presently, it's a feature that will be coming soon...

Let me know how you decide to proceed...

Joel

This discussion is closed. You can start a new discussion or contact Articulate Support.