Just wondering if anyone is using Google's Swiffy to convert some swf files into something compatible with the iPad.
I have tested Swiffy in the past as a simple web link and it works great on the iPad but I'm having trouble getting it to work within Storyline, has anyone been successful in getting Swiffy to work?
No, but I'm looking into this as well. Here is an animation which is converted from swf to html5. Now the only question remains, how to add this to Storyline... It would be so great...since I want to use animated characters with lip sync animations in HTML5 and with a transparent background.....not possible, unless I will use flash objects.
Best chance of success with an externally generated component is to embed using a Web object. That way it'll work in a Flash generated output as well as an HTML4/5 output.
Good timing this thread seeing as I was checking out Swiffy on Fri for the same reasons. I can see using a web object working best for static objects but maybe not for anything that has to move around the screen and maybe change states according to various dynamics. Haven't had a play yet so maybe I'm wrong.
Steve, have you (or anyone) else had any joy with this?
Forget Swiffy, their Base64 encoding makes it hell to make any changes to, for example the background + a lot more problems I encountered
If you can afford Adobe CS6 Flash Pro 12 then you could try Wallaby (I have Adobe CS5.5 Flash Pro 11.5 but isn't compatible)
IMHO I believe the following option is the most viable of all:
Import your character/object in a video editing solution (e.g. After Effects, Premiere Pro) and already embed your desired background. and then simply export your file as a normal (not flash) video file, then insert this video without player controls to Storyline. See Page 2 of the following forum post.
Using a webobject will work but...then each of all the generated content must get their own webpage/link. I think that it would be better and more secure to really embed the graphics/video inside Storyline.
Depends on the type of content. For stuff that's fairly static / non-interactive, I'd lean towards making a video. It'll play more reliably across platforms and will be able to take advantage of the Storyline player. For stuff that I can reproduce in Storyline easily, I'd go ahead and reproduce it within Storyline rather than trying to import.
For stuff that requires complex interaction I can't easily reproduce in Storyline - stuff like interactive simulations that calculate a graphical state - I'd consider two options:
1) Reproducing in HTML4 or 5 and inserting as a Web object. This is only if I really, really care about reaching mobile users with this particular key moment. If it's worth the effort, it's worth the effort. This could be done using Swiffty or another tool.
2) Keeping the Flash version in the published output but branching to a notification screen or alternate on a device that doesn't support Flash. This way, I get to keep the Flash activity in its original form and the user knows where they can get to it if it's important to them (on the desktop). They know what's missing.
7 Replies
Hi There,
No, but I'm looking into this as well. Here is an animation which is converted from swf to html5. Now the only question remains, how to add this to Storyline... It would be so great...since I want to use animated characters with lip sync animations in HTML5 and with a transparent background.....not possible, unless I will use flash objects.
Anyone?
Best chance of success with an externally generated component is to embed using a Web object. That way it'll work in a Flash generated output as well as an HTML4/5 output.
Good timing this thread seeing as I was checking out Swiffy on Fri for the same reasons. I can see using a web object working best for static objects but maybe not for anything that has to move around the screen and maybe change states according to various dynamics. Haven't had a play yet so maybe I'm wrong.
Steve, have you (or anyone) else had any joy with this?
Might give Adobe Wallaby a try later.
Chers
Hi Simon,
To make a long story short:
IMHO I believe the following option is the most viable of all:
http://community.articulate.com/forums/t/7354.aspx?PageIndex=2
I'll be fiddling along. If you have any updates or questions regarding this, please let me know.
Cheers
Wim
@Steve
Using a webobject will work but...then each of all the generated content must get their own webpage/link. I think that it would be better and more secure to really embed the graphics/video inside Storyline.
What do you think?
Wim
Depends on the type of content. For stuff that's fairly static / non-interactive, I'd lean towards making a video. It'll play more reliably across platforms and will be able to take advantage of the Storyline player. For stuff that I can reproduce in Storyline easily, I'd go ahead and reproduce it within Storyline rather than trying to import.
For stuff that requires complex interaction I can't easily reproduce in Storyline - stuff like interactive simulations that calculate a graphical state - I'd consider two options:
1) Reproducing in HTML4 or 5 and inserting as a Web object. This is only if I really, really care about reaching mobile users with this particular key moment. If it's worth the effort, it's worth the effort. This could be done using Swiffty or another tool.
2) Keeping the Flash version in the published output but branching to a notification screen or alternate on a device that doesn't support Flash. This way, I get to keep the Flash activity in its original form and the user knows where they can get to it if it's important to them (on the desktop). They know what's missing.
S
Not yet, I am just also looking forward in using this one. Hopefully, will give me better result.
Thanks,
Ervick of Keka Case Inc.
Dealer distributor of ipad 2 case
This discussion is closed. You can start a new discussion or contact Articulate Support.