As a developer on the Wallaby team, we would like to hear from you about how you are using Wallaby. We are specifically interested in hearing about how you are using Wallaby in a production environment. Any details you could provide about the type of content converted would be great. Conversely, we would also like to know what issues or missing functionality might be preventing you from using Wallaby for production work.
Thank you for your interest Wallaby. Your feedback is critical in guiding the future direction of the technology.
First of all - I love the idea behind Wallaby!
In my mind the biggest obstacle in using it is the lack of Android support. Webkit is used by both iOS/Android but I understand SVG support is omitted from the Android browser (there are some rumors that Honeycomb should correct this). However would it be possible to have some sort of a fallback mechanism in place for browsers that don't support SVG? Like possibly an extra (optional) checkbox to just render everything as PNGs too?
Also a quick question - any idea why html5 wallaby-exported animation is running terribly choppy on my new (dual-core?) iPad2 and yet smoothly on my old iPhone 3GS? Doesn't make any sense.
I'm in the Digital Publishing Prerelease program (creating "apps" or magazines for the iPad.) I wanted to do a cover with a simple slide in animation which I was able to code usings/CSS/html 5. The problem with my coding was that the animation would sometimes load and sometimes not. This was inconsistent and I could not solve the problem. I recreated the animation in Flash and used Wallaby to generate the html/css. The animation performed as desired with one exception--it seemed to slow down the page load very slightly with the result that the background image (whether part of the animation or not) would take a fraction iof a second to resolve - going from blurry to sharp.
Currenty using Wallaby to cut a lot of work. Sencha-touch does not stop animation and importing/editing graphics is time-consuming.
What is needed is actionscript that could be converted into the JQuery instead of css3...dontcha think so? some simple actionscript would be really helpful (the same thing that you did with Flash Lite 1.0 years back in Japan) . Predicting that your team is already working with this.
still need more examples and tutorials regarding understanig so we can manipulate it as per our needs.
Hello, Thanks a lot for your efforts to write a Flash->HTML5 converter.
I understand, that it is currently not supporting AS3 conversion.
I can give you more details, if wished.
To explain: We are developing most of our web-based-stuff with Adobe Flash CS 5.5 and are currently evaluating whether we should continue (this would be the best solution for us, because of the code base and most of all because of the great Flash-IDE Debugger etc.)
With an extended Wallaby, we could write cross-plattform code: for apps and for web and all with one code base (which is AS3, a great object oriented language).
As you see, we are more than willing to support your platform. But for this, we need support from you as well:
1) What is the roadmap of Wallaby (To be honest, I cannot understand why you are not publishing this, this would be a great opportunity for you to sell more Flash CS 5.5 and most of all keep the huge developer base with Adobe)
2) Is it planned, to do more frequent updates on Wallaby (I cannot wait half a year to get a bug fixed, a timeframe of four weeks would be perfect)
Thanks and I am open for every discussion on this topic.
There was something reassuring in CarlMa's remarks, which I share. Somehow, I saw it more Flex -> HTML5 + JS Components (matching all attributes one to one). Either case Wallaby is a great attempt and adventure which I'm sure will export in one way or another the Flash Stage to the HTML5 Canvas through Adobe's SVG, effectively & efficiently. It is obvious that Adobe in a way has an important impact on W3C's HTML5 and web standards through the tools they create for the developer community. As for Wallaby in production, as is today, is fairly primitive and narrow in it's use cases, and but a great endeavour to pursue!
this is completely brilliant! I converted one of my student's animations almost instantly. they're using Flash to create splash pages for their e-portfolios (at my insistence even though some of them are balking due to iProduct and Lion compatibility issues).
I presume it will work on iPads; they will be so freaking happy and so will I!
why aren't we hearing more about this? when will it be updated?
this could be revolutionary!
thank you guys. please finish!!!!!
RMU IAD Professor
I have an .htrml page that previously had two .swf files running on it that I've converted to Wallaby .css/.js animations so that they'll show up on mobile devices. After I had converted the first .swf animation and pasted the code in both the <head> and <body> section, it displays and animates great. However, once I add the second animations code in both the <head> and <body> section, it really screws up how both of them display and animate. Can I not have two running on one page?
Here's the page I'm working on.
It would also be nice to be able to convert .fla files that contain either embedded video or an external video with playback component.