> Which browsers support Swiffy output? > Swiffy uses SVG features that are currently only supported by Webkit-based browsers such as Safari (on desktop and mobile) and Chrome. That's not the HTML5 future I wanted :( In Opera it fails due to JS errors that don't look SVG-specific. It's a shame, because Opera's SVG support is a bit more complete than WebKit's: http://www.codedread.com/svg-support.php (sadly the Swiffy…
Swiffy: convert SWF files to HTML5
61–70 of 77 posts
Re: Swiffy: convert SWF files to HTML5
#62Earlier quoted context omitted.
There's Edit Room, my product, a dead-simple CSS3 animation creation tool. http://edit-room.com/
looks like it could use a little work in firefox 5 before it's at uh, flash level quality: (screenshot) http://www.opencombinator.com/editroom.png
Re: Swiffy: convert SWF files to HTML5
#63Earlier quoted context omitted.
At this point I'm beginning to doubt we'll ever actually get to a fully cross-browser web. We've had two broad reboot attempts (first to "XHTML+CSS", the current one to "HTML5") and both times we ended up largely with a limited list of browsers and engines supported just as we had in the days of Netscape 4.x/IE4. The supported browsers are the cool browsers/engines of the day, which we then proceed to curse in three-…
The cross browser web already exists. It's called AS3. The only reason it gets a lot of bad press is that no one wants to snuggle up to Adobe. Meanwhile everybody flails around pretending that HTML5+JS will solve the problem, when that was already a dinosaur five years ago, and as you said will never be supported uniformly across browsers. Edit: Here come the fanbois to downrate me. Consider your own karma. Downratin…
Just curious what disqualifies the easily googlable Mario Kart and Quake HTML ports?
Re: Swiffy: convert SWF files to HTML5
#64Earlier quoted context omitted.
My experience of HTML5 is that it blows Flash out of the water. Flash on Linux is (still) an absolute disaster while HTML5 is making progress every day and has long surpassed Flash in usefulness for most tasks.
My experience is that your anecdotal experience is flawed and that Flash has a better workflow AND performance AND battery conservation on both desktops and mobile platforms (where it's allowed). http://www.next-gen.biz/news/html5-still-lagging-behind-flas... http://iq12.com/blog/as3-benchmark/ http://workflowed.blogspot.com/2011/02/flash-player-101-for-... http://www.streamingmedia.com/Articles/Editorial/Featured-Ar…
Is this what you wanted to post? This shows that the browsers' JS engines have been outrunning ActionScript for years now...
Re: Swiffy: convert SWF files to HTML5
#65Earlier quoted context omitted.
The cross browser web already exists. It's called AS3. The only reason it gets a lot of bad press is that no one wants to snuggle up to Adobe. Meanwhile everybody flails around pretending that HTML5+JS will solve the problem, when that was already a dinosaur five years ago, and as you said will never be supported uniformly across browsers. Edit: Here come the fanbois to downrate me. Consider your own karma. Downratin…
> The cross browser web already exists. It's called AS3. AS3 is not cross-AS3-player. Does it have two (or more) interoperable implementations? Can it run on platforms not supported by Adobe? While single-vendor closed-source plugin is strictly speaking cross-browser, it doesn't have things we want from "cross-browser" solutions: • freedom to run it on any computing platform (people run HTML+JS on their Amigas, becau…
Re: Swiffy: convert SWF files to HTML5
#66Earlier quoted context omitted.
> The cross browser web already exists. It's called AS3. AS3 is not cross-AS3-player. Does it have two (or more) interoperable implementations? Can it run on platforms not supported by Adobe? While single-vendor closed-source plugin is strictly speaking cross-browser, it doesn't have things we want from "cross-browser" solutions: • freedom to run it on any computing platform (people run HTML+JS on their Amigas, becau…
You're misappropriating the term 'cross-browser'. It does not mean open-source or open. It means the technology will run across most browsers. And Flash does that. You have some valid points but none of them seem to refute the idea that Flash isn't cross-platform.
Re: Swiffy: convert SWF files to HTML5
#67Earlier quoted context omitted.
Flash was built to fill a gaping hole in the market. I think that hole is just about filled (or will be post HTML 5) for the majority of use cases. I see flash falling into smaller niche-based use cases in the near future.
Before this can happen, there needs to be a brain-dead easy to use IDE for creating Flash-like presentations in HTML5. Right now, I see the biggest benefit of Flash being that I can purchase a number of IDE's and create some multimedia (or games) for the web in no time.
I started it when I was in sixth grade, some four years ago and it hasn't changed much in the past two years. Understandably, it's not nearly feature complete. It's actually pretty interesting that when I started out, the goal was to have Flash as the output, because embedding HTML just seemed so impractical.
Re: Swiffy: convert SWF files to HTML5
#68Earlier quoted context omitted.
The cross browser web already exists. It's called AS3. The only reason it gets a lot of bad press is that no one wants to snuggle up to Adobe. Meanwhile everybody flails around pretending that HTML5+JS will solve the problem, when that was already a dinosaur five years ago, and as you said will never be supported uniformly across browsers. Edit: Here come the fanbois to downrate me. Consider your own karma. Downratin…
I think you're getting downvoted for implying that something can be "cross-browser" that is locked into a single vendor. Your point is clear, but it exploits a nerdy little loophole in the definition of "cross-brwoser".
Look, the only reason there's ANY implementation of ECMA4 in the browser, i.e. Flash, is that a company which doesn't make a browser took it upon itself to create a plugin for all browsers that runs it. Now everyone hates them because it's "closed", which is ironic because IE's implementation of for example the matrix 'filter' -- just to pick one random thing -- is so ludicrously archaic and different from anything webkit, that there's zero, zip, nada, NO HOPE of those two things ever converging in a way that would let a single piece of code skew the same image in both browsers.
Anyway, to other people -- I work on mac, and I write code for both canvas and as3. I wrote this: http://strikedisplay.blogspot.com. Also wrote sexypolitics. Things are...what they are. You have to face reality and use the right tool for the job. And when JS2 comes out, sure I'll be there. 'Til then, long live Adobe. Beats the alternative Mozilla/Microsoft/Google mess.