4 ms·
> Which browsers support Swiffy output? > Swiffy uses SVG features that are currently only supported by Webkit-based browsers such as Safari (on desktop and mo
by pornel 15y ago
> 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 http://www.codedread.com/svg-support.php (sadly the Swiffy's site doesn't say exactly which feature it needs)
Anyway, it's great that they're using SVG. Good use-case for SVG will help it get more love from browser vendors, and perhaps developers won't have to reinvent SVG with canvas :)
- jbwyme 15y agoI don't think this is indicative of the future of HTML5 and I'm not so sure there will be a reason to use these SWF->HTML5 converters other than maybe a head start on re-developing your application. Have you tried converting a PDF to word? Converters for proprietary technologies haven't proven to be very effective.
- whatever_dude 15y agoThe problem with both converting SWF and PDF into more 'open' formats is not that they're proprietary (SWF specs are freely available no anyone; not sure about PDF) but that they're final formats. PDFs, for example, retain information about how something should be rendered, not edited; hence why blocks of text get cut when trying to convert it to anything (there's no text flow information). In the same way, images are downscaled, transparencies are flattened or rasterized, fonts are broken down... there's too much lost. A SWF is the same; it'd be better to work from original files and projects (similar to what Wallaby is trying, and maybe Hype?) to 'compile' everything to HTML5 (or whatever output format) than trying to transcode something from a format that was optimized for one specific kind of player.
- jarek 15y agoAt 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-four years. Only the names of the browsers change. Edit: heh, didn't even notice who I was replying to.
- noduerme 15y agoThe 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. Downrating me does not change the facts on the ground. You cannot build a 3d racing game in HTML5+JS in the browser. Can you??? If you can, seriously, respond instead of hitting that little down arrow, and I would love to see what combination of technologies you employ!
- CodeMage 15y agoUnfortunately, you are at least partially right. HTML5+JS might be an acceptable solution to lots of problems, but I don't see web game development moving away from stuff like Flash and Unity to a W3C standard. It probably has a lot to do with having to wait forever while the W3C labors to push any damn thing out.
- tptacek 15y agoI 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".
- evilduck 15y agoNot only that, but Flash isn't perfectly "cross-platform" either. It's really only a great experience on Windows and 32 bit and a crapshoot everywhere else, it's still the major cause of browser crashes everywhere else, has struggled with 64 bit implementations, has a long history of sandbox security problems, and their feigned "open source" efforts where there's proprietary parts they don't document or release garners them few OSS friends, downgrades poorly, is a significant resource requirement overhead, and isn't very accessible by default (the standard swf you encounter will not be blind-user accessible). If Flash is the answer, we're in even worse shape than using HTML/JS.
- mbrubeck 15y agoIt seems to mostly work out of the box in Firefox (tested in Aurora 6.0a1), although there were a few elements in some of the demos that did not render correctly.