No Compatibility for AS2 FLAs? Absurd.

Question

Will you consider adding compatibility please??
Love the dark interface - been waiting a long time for that actually. Never knew why it didn't happen when Photoshop got it. But very dissapointed that I cannot open FLAs with AS2 in them, perform an update, and simply export them back out.
Yea yea... I heard it - Adobe doesn't "support" AS2 anymore. But that doesn't mean that new products we are paying for should have zero "compatibility" with our previous work. Opening , editing, and closing an AS2 -based FLA file does not mean I am refusing to get on board with AS3 after a million years. It is a simple necessity. I prefer AS3 for coding to AS2. I get the focus on the latest scripting rev. I get that it uses the better VM that runs 10 times more efficiently blah blah - so better for mobile etc. (probably the motivator here). So, no longer "supporting" AS2 programmers - as in being there to help/encourage people who still write it etc - is understandable at this stage. BUT to disable the ability to open a legacy file with AS2 in it - perform a simple edit and reexport it - is a horrific decision. Here is just one real world example of why.
The group I work with has developed HUNDREDS of learning modules and tools over the last DECADE using Flash. Some of tools are complex interactive games etc - that require updates from time to time based on requests. Am I supposed to entirely recode them so I can use my new software? This as opposed to spending 15 minutes on an update and export? Each lesson module uses a custom designed AS2-coded shell environment that loads - on average - 30-50 external swf files - all coded in AS2 themselves because the shells cannot load AS3. To go backwards and reprogram the shells themselves (very complex), as well as all the interactivity and videos and buttons and audio and testing that is inside these shell-loaded swf files (numbering in the thousands likely) would be an enormous and absurdly wasteful undertaking.They regularly need small or minute updates to their content - mere text changes here and there even - previously taking only minutes to perform. Now, if I export the swf, it will be AS3 and won't work. These updates are done regularly. Are we supposed to now say "hey - client - guess what - your stuff needs to be completely retooled for no good reason - even tho it runs beautifully as-is" ?? I can't even open an FLA and export it out if it has AS2 in it??? I don't expect Adobe "support" in regards to new AS2 projects, but backwards "compatibility" is another thing. Some people have a ton of work still being used on a regular basis that was written prior to AS3 being the standard - and the clients don't care about AS3 - they care about their budgets.
I will have to keep Flash CS6 installed apparently, even tho I pay 50 bucks a month for the CC. Flash - for many of us interactive devs, who build stuff for government contracts and/or big companies that are still running IE7 and IE8 across their corporations (with no intention of updating anytime in the near future - believe it) have no option other than Flash, so we still spend an incredible amount of time in this tool. I can't just kick out static down-staged images for these guys with my magical Edge Animate software. Great product too - which I use for other things - but not the silver bullet of online animation/interactivity by any stretch of the imagination.

Answer 1

I feel ya The Jayster
Here is my rant...
I work for a large company with a ton of legacy files that need updating periodically.
Just had to work on something just the other day because the path to a server needed updating.
This would be impossible to do in Flash.CC unless I recoded the whole app.
Nobody is going to pay for that when it works perfectly already for years.
If you have to maintain legacy code for several sites you need to be able to edit any file you have ever created.
I started out with Flash 4 ( 1998 ) and have had every single version since.
Even when there was very little offered in the upgrade.
I will not be using Flash.CC though.
1) I need to edit legacy files.
2) I will not rent software.
3) I do not agree with the restrictions imposed by CC
4) There is no way to edit new files created in Flash.CC if you quit.
Saving as CS6 version will loose forward features added in Flash.CC
( Exporting to Dart would be an example );
I could think of more reasons but whats the point.
These are my gripes with Adobe.
1) Went to a "rent to use" software model.
2) Ended support for mobile browsers.
3) Removed design view from FlashBuilder.
4) Cant edit legacy files in Flash.CC
I am also sad to see Fireworks go bye bye.
That was also in my original Macromedia Suite along with Dreamweaver.
I have upgraded those too over the years.
I'm sure that Dreamweaver will be next on the chopping block.
Guess we have little choice but to stick with what works.
I have recently been tasked with converting our video chat product to HTML5/CSS3/JS
I decided to use Sencha for the framework.
Although I have been able to recreate the interface and most of the functionality there are some huge roadblocks only Flash can handle.
1) Broadcast your Webcam/Microphone via any Desktop browser or Mobile app.
2) RTMP support for live video encoded from a browser or app, RemoteSharedObjects and onSync events.
So I guess I will be stuck in the muck along with you.
Shame on Adobe for self destructing and alienating its long time fatefull customers.
I have always been gung-ho for Flash but my ho's been gunged.