One of the reasons we like Flash and Flex is because it gives the consistent visual results across platforms. I'm a little concerned that we are adopting JS and HTML approaches and will then inherit it's problems. IE leaving the view to HTML.
One of the potentials I see in the Flex to HTML / JS projects is that we will eventually be able to create the same app from the same code base and get the same look and feel as we do in Flash Player / AIR. If we have to start worrying about visual inconsistencies between browsers or export HTML and CSS with patches for different browsers then what is the advantage? I know there is an advantage. It's that we can use AS instead of JS so you get all the advantages of AS, like a strongly typed languages, packages etc. I think that's the Randori approach. That's a huge. But it doesn't address the view. At the end of the day we would still need to write the view in HTML or in your version of Flex use raster images instead vector graphics? Correct me if I'm wrong. I'm still in a wait and see. I'm interested in seeing if we can get the same vector output in HTML as we do in Flash. I think Frank mentioned he has a Flash JS runtime container that runs on the HTML Canvas (charts demo?). I would rather we target that (HTML canvas, drawing API), even if it's poorer performance at the present time. We can always do runtime performance measurement and turn off some or all of our animations on slower browsers. But from a quick look online I'm reading many / all the major browsers are hitting 40 to 60 FPS for HTML Canvas on similar drawing calls to what we have in Flash. I can look into HTML5 performance and how it performs across browsers (mobile may be much faster than desktop?). I'm sure Frank has the numbers and more information on this so I'll wait here before looking further into it reply. I bring this up because I've been writing mobile and desktop app and in my view for my apps, vector support is becoming much more important than I thought as I target more platforms (and now retina displays). I'd argue more for consistent look is more important than performance. That's like a holy grail and major pain point in HTML development (or was for me). I don't know. Thoughts? My 2 cents. On Thu, Mar 14, 2013 at 9:58 AM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/14/13 2:53 AM, "Sebastian Mohr" <flex.masul...@gmail.com> wrote: > > > > @Adobe folks ... > > What's wrong with continuing to provide design tool support for > > Apache Flex? How else should we skin Apache Flex components? > Don't know. I would assume it is a matter of resources and time. > > FWIW, the new framework I'm working on is probably going to be less vector > graphic oriented and rely on bitmaps since I think bitmaps are how most > things get "skinned" in html/js/css > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
