Adobe Flash Professional Team Blog

The latest news, tips and insights directly from the Flash team

December 18, 2012 /

Exciting changes to Flash Professional in 2013

Hi Everyone,

In 2013, you’ll see dramatic changes to the next version of Flash Professional. We’ve been hard at work making the next generation of Flash Pro faster, more reliable, and more extensible. These and many other changes are paving the way for the tool to stay ahead of the curve, for many years to come.

The changes include making Flash Pro more focused and efficient. With twelve releases under our belt, there are a number of legacy features and support for older technologies that are losing relevance. In order to make Flash Pro more streamlined, we had to make some tough decisions based on customer usage and feedback, on what we should no longer support.

One of the key changes in the next version of Flash Pro is dropping support for AS2. As you may know, we introduced AS3 six and a half years ago, and today it is the most widely used language for the Flash Platform. Given AS2’s dwindling usage and misalignment with the future of the Flash runtime such as AIR mobile app development and Stage3D, we felt it made sense to move forward with AS3 only.

We understand this change impacts those of you who continue to use AS2, and hope this gives you time to prepare for the transition. Please note that AS2 content will still work in Flash Player (and future versions of it).

We’re really excited about what’s coming for Flash Pro, and can’t wait to share more details with you. Stay tuned to this blog for sneak peeks and more after the holiday break.

Cheers,
Rich Lee
Product Marketing Manager

Categories: ActionScript, General

Comments

  • […] on blogs.adobe.com Share this:TwitterFacebookLike this:LikeBe the first to like […]

  • By David - 12:27 PM on December 19, 2012  

    If the changes are like the ones from CS5 to CS6 I’ll not move, actually, for designers and animators there haven’t been important changes since Flash 8, wich is quite dissapointing.

    • By Rich Lee - 11:07 PM on December 19, 2012  

      Stay tuned for sneaks next month…we think you’ll like it!

      • By Jarkko - 4:38 AM on February 4, 2013  

        “next month” is now last month. Any news about the sneak peeks?

        • By Rich Lee - 2:39 PM on February 4, 2013  

          Hi, sorry for the delay. We will have more info soon. Thanks!

          • By Andrew Doll - 4:14 PM on March 26, 2013  

            Also very interested in these updates….any news?

  • By Stuart - 2:15 PM on December 19, 2012  

    cool cant wait!! gonna get more deeper into flash now

    • By Rich Lee - 11:07 PM on December 19, 2012  

      Awesome!

  • By Israel Lazo - 4:32 PM on December 19, 2012  

    I really think that if someone is going to stick with AS2 doesn’t see a real value of updating flash

  • By Konstantin - 1:01 AM on December 20, 2012  

    You’d better add a good code editor to it, so people could used it without some third-party IDE’s or event flash builder. Flash CS X’s code editor still sucks.

  • By Corstiaan - 1:56 AM on December 20, 2012  

    I’m reading “dramatic changes” as “Fix it so it crashes less”. But I’ll give Adobe the benefit of the doubt, maybe they’ll adapt the interface to comply with all other Adobe products now (key-shortcuts, spline-working, use of spacebar after drawing, colorpickers..). And maybe we can work with shared assets, frame-copying and fonts reliably in the futute.
    Good luck!

  • By Tsafi - 2:07 AM on December 20, 2012  

    thank you ,its a bout time,to bad you didn’t do it 2 years ago

  • By Xelu - 2:37 AM on December 20, 2012  

    how about hotkeys for more useful actions like “transform lines to fill” and making the actions window dissapear by double click again.. why on earth would you have that in CS5 then remove it? :(

    Also many many other things that bother me, I should make a list =)

  • By Jim Thomson - 8:21 AM on December 20, 2012  

    I just coded a webpage using jquery with a dropdown menu, accordian style table of contents and a slide show in 47 lines of code. That’s how easy Flash should be.

  • By Mark - 10:31 AM on December 20, 2012  

    I hope all stupid bugs are fixed that haven’t been fixed in the last versions, and add some really new good features that improve work-flow to create dope experiences. To be honest, CS5 and CS6 were very disappointing, so please let us see you care about the users who use your software. But since you do make decisions based on customer feedback, here is my wishlist, in case you did not fix them already.

    – Fix the cancel-button while compiling. You know what I mean, frustration.
    – It won’t crash after dropping a new MovieClip from library, when you have Photoshop with big documents open for a while.
    – Fix when press ‘export for runtime’ on a MovieClip properties, the classname does not get reseted, so annoying.
    – 9-slice on bitmap should work without manually break into groups
    – Drop the ‘graphic’, add the ‘Sprite’ (no frames).
    – When extending Sprite, it should give warning inside IDE you cannot use frames.
    – A random frustration: CS6 fla files cannot be opened in CS5. I understand that is marketing-wise a good thing, but (be honest) since there isn’t changed anything in CS6 that could impact on CS5, it should be possible to make it work in the older versions, maybe with a warning of losing version-specific info.
    – Provide a better filters-panel, like Photoshop, only with the ability to add multiple of the same filters.
    – Create a better commands-menu, if you have lots of jsfl scripts and/or use folders. Currently, its buggy.
    – Or if pc is using too much memory, hundreds of library-items, layers or scenes will be created or the timeline doesn’t update instant. If you save the file, its corrupt and unfixable. This happens to bigger .fla files with lots of assets.
    – Remember swatches over multiple files. It would be cool to have dynamic swatches too (when alter color in panel, it would change in full document)
    – Better support for runtime shared fonts (styles) and multiple fonts in 1 textfield.
    – Give us a underline-button at the text-tool properties panel.
    – remove window>toolbars>Main and window>toolbars>Controller, you forgot to remove it in CS1, you cannot pin them into any other toolbar.
    – An instance name should not be different on the same layer at another frame. So just drop the ability to change its name on another frame. If you change it, it should change over the full layer.
    – When you have frames on your mask-layer and have code attached to any, stuff is going wrong, debug that.
    – Drop the bone tool, the decorator tool, and don’t even try to add a new thingy like it. Nobody ever used it, or was very disappointed by it’s limitations.
    – Drop ‘scenes’
    – Did you know you can use ctrl + hold middle mouse-button + scroll on the timeline and some panels? It scales, but not smoothly.
    – Make ‘snap to pixel’ actually always round to pixel
    – Next to the lasso tool, add a polygonal selection tool.
    – I would love to see an ‘inner line’ and ‘outerline’ option, also in Graphics-api class on lineStyle() function. now it is always centered around its shape.
    – If you want to promote the Flash IDE with a panel named createJS and have wonderful html5 integration bla bla, then at least at it to the IDE, don’t let me download it manually.
    – Don’t force focus on the IDE while compiling, I want to read facebook while compiling.
    – Add a column ‘base class’ to the library.
    – Default set the audio quality a bit higher, 80kbps sounds very crappy.
    – Give us more compiler options, make the target versions editable in a way, since they update faster than the IDE.
    – Multiple layer guiding/unguiding.
    – When duplicate a runtime shared symbol in your shared assets file, don’t import it as runtime shared asset that links to the same file.
    – Make duplication of symbols more easy, remain the class references etc.

    BTW: Isn’t as2 still *needed* for banners?

    • By Mario - 5:18 AM on January 24, 2013  

      AS2 is still allowed for banners, but not needed. At least in Austria and Switzerland. Anyway, a lot of banners are still using AS2, because everybody is just reusing old stuff. 😉

  • By Tufik - 11:18 AM on December 20, 2012  

    Would be very good and very exciting create full business aplication for our clients, games and all content with native code and don’t begin to leave the native code in the cabinet by using frameworks like Starling.

    Starling is a very good framework, and thank to they for improve AS3, but i would like work with all this functionality with the navite code and don’t neglected this, i think that is the result to the abandonment and a bad support of Adobe.

    you do not believe, AS3 has the best and professional UI call Flash Professional for create good interface and the job is simple, didactic and quickly, there aren’t other IDE like this for implement and work with the interface, if you want you can export all to swc and begin to work with a developer IDE like, Flash Builder or FlashDevelop (my favorite IDE). But lately things like MovieClips, Sprite, native events are increasingly far. Now we should use Starling, Feathers, Haxenme, all less native classes for get a best result.

    Another thing, Adobe should think in get support to all Android devices. This is the most big problem of Adobe Air and prevents that Adobe Air be imposed, because in my case, i can’t offer this to my clients because don’t have support for all devices and the most important for do a professional aplication for a enterprise is support to everyone with android devices. The problem is that Adobe don’t know the real power of this tecnology and the all community working with this (developing app and not game).

    What do you think?

    • By David - 6:50 PM on January 2, 2013  

      Yes, I totally agree.
      Adobe please don’t ignore business application that can be done with your technology.
      AS3 is for sure the best tool to create good UI.

    • By Jasur - 2:54 AM on March 5, 2013  

      Agree with you. For 2 and half years I am creating only business applications with AIR technology and always welcome when new updates/features are added. In my opinion Adobe must think both app and game, not focus only gaming.

  • By Mark - 11:52 AM on December 20, 2012  

    I hope all stupid bugs are fixed that haven’t been fixed in the last versions, and add some really new good features that improve workflow to create dope experiences. To be honest, CS5 and CS6 were very disappointing, so please let us see you care about the users who use your software. But since you do make decisions based on customer feedback, here is my wishlist, in case you did not fix them already.

    – Fix the cancel-button while compiling. You know what I mean, frustration.
    – It won’t crash after dropping a new MovieClip from library, when you have Photoshop with big documents open for a while.
    – Fix when press ‘export for runtime’ on a MovieClip properties, the classname does not get resetted, so annoying.
    – 9-slice on bitmap should work without manually break into groups
    – Drop the ‘graphic’, add the ‘Sprite’ (no frames).
    – When extending Sprite, it should give warning inside IDE you cannot use frames.
    – A random frustration: CS6 fla files cannot be opened in CS5. I understand that is marketing-wise a good thing, but (be honest) since there isn’t changed anything in CS6 that could impact on CS5, it should be possible to make it work in the older versions, maybe with a warning of losing version-specific info.
    – Provide a better filters-panel, like Photoshop, only with the ability to add multiple of the same filters.
    – Create a better commands-menu, if you have lots of jsfl scripts and/or use folders. Currently, its buggy.
    – Or if pc is using too much memory, hundreds of library-items, layers or scenes will be created or the timeline doesn’t update instant. If you save the file, its corrupt and unfixable. This happens to bigger .fla files with lots of assets.
    – Remember swatches over multiple files. It would be cool to have dynamic swatches too (when alter color in panel, it would change in full document)
    – Better support for runtime shared fonts (styles) and multiple fonts in 1 textfield.
    – Give us a underline-button at the text-tool properties panel.
    – remove window>toolbars>Main and window>toolbars>Controller, you forgot to remove it in CS1, you cannot pin them into any other toolbar.
    – An instance name should not be different on the same layer at another frame. So just drop the ability to change its name on another frame. If you change it, it should change over the full layer.
    – When you have frames on your mask-layer and have code attached to any, stuff is going wrong, debug that.
    – Drop the bone tool, the decorator tool, and don’t even try to add a new thingy like it. Nobody ever used it, or was very disappointed by it’s limitations.
    – Drop ‘scenes’
    – Did you know you can use ctrl + hold middle mouse-button + scroll on the timeline and some panels? It scales, but not smoothly.
    – Make ‘snap to pixel’ actually always round to pixel
    – Next to the lasso tool, add a polygonal selection tool.
    – I would love to see an ‘inner line’ and ‘outerline’ option, also in Graphics-api class on lineStyle() function. now it is always centered around its shape.
    – If you want to promote the Flash IDE with a panel named createJS and have wonderful html5 integration bla bla, then at least at it to the IDE, don’t let me download it manually.
    – Don’t force focus on the IDE while compiling, I want to read facebook while compiling.
    – Add a column ‘base class’ to the library.
    – Default set the audio quality a bit higher, 80kbps sounds very crappy.
    – Give us more compiler options, make the target versions editable in a way, since they update faster than the IDE.
    – Multiple layer guiding/unguiding.
    – When duplicate a runtime shared symbol in your shared assets file, don’t import it as runtime shared asset that links to the same file.
    – Make duplication of symbols more easy, remain the class references etc.

    BTW: Isn’t as2 still *needed* for banners?

  • By Darshan Rane - 12:58 AM on December 21, 2012  

    I will second Konstantin comments, that we need a proper code editor, so as we can avoid using third party tools.

  • By Sai - 2:15 AM on December 21, 2012  

    I don’t think it’s the good idea to drop as2 when especially html5 is around . I predict most of the designers will learn html5 instead of learning as3 due to cross platform compatability .

  • By Al Lemieux - 1:16 PM on December 21, 2012  

    You absolutely have to fix the font engine in Flash. There are so many problems with TLF, font embedding, and foreign language characters in dynamic text in Flash. CS6 didn’t fix those issues either.

    Come on Adobe. You practically invented Postscript and programs like InDesign, why can’t Flash have broader text features and controls?

  • By Darshan Rane - 11:24 PM on December 21, 2012  

    Yes, we need a better code editor. Also as the AS2 will not be available in new version, i think we can still develop in it through older version….

  • By ghasan - 8:00 PM on December 23, 2012  

    are we about to have support for windows mobile 8 ?
    and blackberry 10 ?

    any changes to air sdk ?

  • By civet - 12:00 AM on December 26, 2012  

    As an animation editor, the features of Flash Pro are out of date! Bitmap do not support filters, morphing etc.
    As a UI editor, the peformance of is so poor, and Flash Pro made a mess of MovieClips.
    As a IDE, it only fit for simple work. Layer managment is not always good! Not any tree diagrams to show how to treat with complex displaylist on Stage, to say nothing to performance optimization.

  • By Jonathan Kaye - 7:52 PM on December 26, 2012  

    I can certainly understand your reasoning, you’ve given AS2 enough time. That having been said, because of the amount of work likely still in AS2, I would urge you to continue offering a legacy version, CS6, or maybe an earlier version of Adobe Flash (Adobe Flash Classic?) rather than what seems the typical pattern of erasing the potential of buying an earlier version except through second-hand markets like eBay and such. Especially since AS2 projects will continue to work through the Flash Player.

  • By Roy Casella - 1:40 AM on January 3, 2013  

    Great to hear that Flash Pro is getting some real effort put into it.. well done..

    However, with Flash dead on mobile devices… where does this leave Flash as a technology for the future.

    Interested in your responses as we need to decide where to put our efforts as tablets etc… are becoming more and more commonplace in the working and consumer world.

    Many thanks and looking forward to your replies.

    Roy Casella

    • By Rich Lee - 4:15 PM on January 7, 2013  

      Hi Roy,
      Thanks for your input, we are working hard on the next version of Flash Pro. Flash is still great for mobile apps with AIR, and keep in mind that you can use the Tookit for CreateJS extension (for Flash Pro CS6) to convert content to HTML5.

      Cheers,
      Rich

      • By Tufik - 1:31 PM on January 9, 2013  

        Hello, if you would like than the developers used this tecnology for mobile, you should give a full soport for all devices. I am a developer for mobile i love AS3 but i can’t see a Adobe Air like a real tecnology for develop mobile content because it don’t have support for all devices in the current time and the principal reason when you develop an comercial aplication, you can’t say to the client, your aplication is incompatible with some android devices. In the present is very precise say that the Adobe Air tecnology don’t will have a good success for this reason.

        In the passed the filosofy of Adobe with AS3 was, develop for all screen, what happened with this filosofy.

  • By Tim - 3:45 PM on January 6, 2013  

    #1. Review the long forgotten ‘Adobe Ideas’ site where the community listed the various bugs they wanted fixed, and features they’d like implemented or enhanced (Not to be confused with the new touch app!).
    #2. Fix the various UI bugs which have existed since MX 2004!*
    #3. Finally give Flash Pro it’s its own bug tracker at http://bugs.adobe.com

    * e.g. Whatever causes the Import to Library dialogue to randomly switch/default to AI files only or PNG files only instead of All Formats when working on an FLA for an extended period.

    • By BD - 2:37 AM on February 7, 2013  

      Yeah! How usefull would that be? A central place that your clients / community can submit, discuss and view progress on bugs & features… What a concept!

  • By Tufik - 1:31 PM on January 9, 2013  

    Hello, if you would like than the developers used this tecnology for mobile, you should give a full soport for all devices. I am a developer for mobile i love AS3 but i can’t see a Adobe Air like a real tecnology for develop mobile content because it don’t have support for all devices in the current time and the principal reason when you develop an comercial aplication, you can’t say to the client, your aplication is incompatible with some android devices. In the present is very precise say that the Adobe Air tecnology don’t will have a good success for this reason.

    In the passed the filosofy of Adobe with AS3 was, develop for all screen, what happened with this filosofy.

  • […] Exciting changes to Flash Professional in 2013 « Adobe Flash Profes…2012/12/20 this change impacts those of you who continue to use AS2, and hope this gives you time to prepare for the transition. Please …はてなブックマークより […]

  • By Shawn - 6:06 AM on January 31, 2013  

    Just make sure you add a lot more Code Snippets for us designers.
    I design a tonne of flash banners both in AS2 and AS3.
    The Code Snippets are great and it speeds up my ability to crank out banners.

    Can I give One Suggestion? Can you add the ability to “Export a movie” as another file type othe than quicktime? For example MP4? – Thanks

  • By Andrew - 8:58 PM on January 31, 2013  

    – Better code hinting like Flash Builder would be nice

  • By Christian - 2:01 PM on February 4, 2013  

    Will the new version have the ability to open up previous flash files with AS2 in them? We have flash files with AS2 and would like to be able to update them to AS3. We would like to know will we have the capability if we upgrade. Thanks.

    • By Rich Lee - 2:38 PM on February 4, 2013  

      Hi Christian — Yes, you will be able to open FLA files that contain AS2, and then you can manually update the code to AS3. Our product team has noted two exceptions though:

      1. AS2 code attached to any instance on stage will be removed (because actions on instances is not supported in AS3)
      2. AS2 components will be carried forward as placeholders, but cannot be used to create new content on stage. Also, they will generate compile errors in AS3.

      Thanks,
      Rich

  • By BD - 2:39 AM on February 7, 2013  

    Have a look at what these plugins do: http://www.trickorscript.com/plugins.php
    Simple things like “delete all empty layers” a “library manager” would be nice…

  • By Andie Marz - 3:37 PM on February 7, 2013  

    Hi,

    I teach Flash and I see a steep decline in number of students last year. I don’t think people know what Flash is for now that there is no browser support. People think that Flash is dead. Does Adobe has any hope of Flash ever come back to play a role on Internet environment? what is the purpose of using Flash and Actionscript now? Why should people invest their time learning Flash, or developing their skills in Actionscript 3.0?

  • By sanjeev - 7:30 PM on February 26, 2013  

    good decision…

  • By Matt - 10:31 AM on March 14, 2013  

    Agree with many above suggestions. Not sure it was listed but please implement the following:

    1. Allow the ‘FIND’ dialog to remain open and edit code simultaneously. Even MS Notepad has this capability.

    2. Flash Pro can currently designate Flash Builder as default code editor. When I compile with Flash Pro, the compiler catches the error but instead of jumping Flash Builder to the line, it opens the AS3 file in Flash Pro to the error. Needs to be more seamless integration.

  • By aconma - 8:56 PM on April 17, 2013  

    Brings code hinting back to Flash Pro is the best new feature, I think.

  • By tfbkny - 12:38 PM on May 4, 2013  

    Any followup to this blog post made in December? I haven’t seen any… has anyone? If so please share a link. thanks :)

  • By James Spielvogel - 9:46 AM on June 3, 2013  

    Good riddance to AS2. Add the UNDERLINE button for classic text!!! It’s long overdue and causing no end of headaches having it missing. The Text Layout Framework (TLF) is unusable in the current state as of Flash CS6 thanks to its terrible (pre)loading architecture, particularly this issue with ridiculous workarounds (http://helpx.adobe.com/flash/kb/loading-child-swfs-tlf-content.html). Make the TLF classes intrinsic to the Flash Player, so it doesn’t have to be downloaded separately or embedded into every file that uses it.

    Add a TEMPORARY or TEMPLATE LAYER type, which can be locked but remain visible which is not compiled into the final SWF. I used to use a mask layer (with no masked content) to achieve this in Flash 8, but now when you lock a mask layer it becomes invisible, so it’s useless for acting as a layout template. You can actually see the difference in behavior if you start by targetting Flash 8, then target Flash 11 for example. The locked masked layer is visible, then it becomes invisible once the target player version is changed. Alternatively, add an option to masked layers so that the mask remains visible when locked.

    The code hinting and other code management options are terrible in Flash. Often I don’t even get code hints. FlashDevelop app beats the ass of the Flash IDE when it comes to code. Come on.

    Some sort of deep copy option in the library would be nice for duplicating clips. The “duplicate” option does not do such a deep copy, where all nested objects are copied, however, I have noticed that this can be achieved by copying a folder. It’s just not obvious. Have someone work on that, please.

    SCREW JSFL, ALLOW US TO SCRIPT FLASH WITH FLASH!!! Create an AS3 API for the Flash IDE, or improve JSFL and it’s documentation. I love the WindowSWF feature, but it would be AMAZING to not have to call MMExecute, and instead just be able to do everything in AS3.

    • By Amy - 6:47 AM on June 24, 2013  

      James;

      I think the temporary/template layer you are looking for is called a “guide layer.” Just right-click and select “Guide.” If this is not what you want, how is it different?

  • By Paul - 7:07 AM on June 18, 2013  

    I was totally dependent on AS2. Unfortunately AS3 does not provide the simple solutions that I need (Projector file is a big one). It’s sad that there is not support for 2. Adobe is phasing me out.

  • By Nick - 1:05 PM on June 25, 2013  

    I just want the Motion Editor Back.. without it making accurate tweens is like typing with mittens on..
    I am going to have to go back to CS6.

    • By ajaykumarshukla - 9:28 PM on December 11, 2014  

      Now that a redesigned motion editor has released, we’d like to hear your feedback.