My clients simply aren’t interested in technology or long conversations about the future of Flash / HTML etc – they simply want the websites to work and look great (without spending huge sums of money on development).

My question is whether this new export to HTML features will work with AS2 code and not just AS3 (a lot of us designers simply can’t get our heads around AS3 code which takes much longer to code – we like hacking ideas together quickly in AS2) – and of course whether it is just limited to animation (ie like Google Swiffy) ?

I hope output to JavaScript isn’t the only thing Flash can do though – I use Flash mainly for generating SWF files, which are conveniently packed into one single file that can be executed whenever desired. There is no web equivalent to do that, save for the MHT format.

there is hardly anyone who knows what is going on in this company.

The awful thing about this HTML5 transition is that this encapsulated, single file transport that simply works anywhere will be a thing of the past.

Flash was one respite shelter from the madness that is developing for compatibility in nutty browser city. It’s sad to see this respite come apart at the seams as the misguided influence continues to spread. “Kill Flash” is a common mantra. It’s not a pretty sight. And it seems to get worse every week.

While these moves and opaque news releases that do real damage to your Flash developer community may end up increasing your revenues, you’re doing even greater damage to the trust relationship you have with the Flash development community by not dealing with these problems in a positive way.

is that idea a good idea ?

is-it the truth to only tell : generating HTML5 ?

Is-it not more accurate to say : Flash Pro generating HTML5+Javascrit+CSS
and to tell us in which extended versions (.x) if accepted by the HTML5 community with Apple, Microsoft and others ?
or in the very limited actual versions with one different flavour for each member of the “pseudo community” ?

Are the capabilities and qualities of Flash and HTML5 the same ?

So in the real world and in every day practice, this generation will fail very often, no ?

and it will be necessary to always verify and return to Flash to simplify and adapt the flash source
to the extreme limitations of the HTML5 targets and flavours, no ?

And all this “bad work” is not a “forward work” but a “regressive work” and a “not efficient work”
which consist to go from a more powerful tool like Flash with its “code once” and “play everywhere the same result”
toward a less powerful tool like HTML5+Javascrit+CSS.
IT’S A NONSENSE WORK ! for Flashers of dream team !

And how to explain now to our client that we have been obliged to extremely simplify and cut into his needs
because of the impossibility to generate that he was waiting for in HTML5 + Javascript + CSS ?
And to explain him also that the size of this simplified and truncated version generated in HTML5
is far more heavy than the flash full and complete version and also far more slower and with less performance ?

What a good job Adobe anti-Flash GUYS !
Thank-you Steve and Apple and Microsoft and financial analysts !

What a good Future you build GUYS for Flash developers !

I hope you are not paid at ADOBE with our Flash Pro license fees
but only with your Apple and Microsoft arrangements…

We are NOT so STUPID !

If there is a good Job to do, there is only one WAY :
to completely open source the Flash Player code for the world community
and integrate it in the basic WebKit code for all browsers in the full and same way
for a full web experience everywhere on every browser and device platform mobile and not mobile.
And then : the problem is resolved ! not transformed in a no way pseudo solution that doesn’t work !

So I say you GOOD BYE !

Flash developer and designers can use their Flash skills and by exporting application into HTML to target more platforms and mass audience.

Nevertheless these are the types of features that needs to be exported to. I wish it started a little earlier though.