Note: As of November 2015, Edge Animate is no longer being actively developed. Learn more.
The 2015 release of Adobe Edge Animate CC includes support for in-line text that lets you type and edit text directly on Stage. This release also includes a bunch of bug fixes for crashes and overall stability of Edge Animate.
In the previous releases of Edge Animate, you used to type text in a popup that later appeared on Stage. In this release, you can type text directly on Stage. You can also format portions of text (referred to as text spans), which was not supported earlier.
The text box in this case is auto adjusted to the text you type in. If you want to define your own text box and then type the text, do the following:
To format a portion of text differently from the rest, select the required text and use the Properties panel to modify as required.
The 2014.1.1 release of Adobe Edge Animate CC provides many important bug fixes including crash issues while using Timeline and reordering of elements. This release also includes fixes to issues with audio/video and scroll effects workflow in Adobe Muse, along with new runtime APIs (getSymbolTypeName and symbol.seek).
The earlier versions of Edge Animate runtime used to depend on jQuery internally. jQuery was always added as a dependency in your composition irrespective of whether you are actually using any of the jQuery APIs or not. This dependency is removed in the latest Edge Animate Runtime, which means a smaller payload size and reduced number of downloads required for running your compositions.
The requirement for a separate preloader js too is removed in this release. Edge Animate now generates a single js file for your composition, which contains the entire DOM and your complete code in the Edge Animate composition.
Compositions created using previous versions of Edge Animate are automatically upgraded when you open them with this build. The upgraded composition along with the associated files is saved in a separate folder under the root of the project folder.
For example, if the previous composition is in the /user/MyProject folder, the upgraded composition will be in the folder /user/MyProject_upgraded. Assets that are directly referenced in the composition are automatically copied to the upgrade folder. You may need to manually copy the rest of the assets that are not directly used in the composition (for example, additional CSS files, assets used only through scripts).
Also, due to new runtime changes described below, any jQuery dependencies in the previous compositions are added as user scripts to the Library in the upgraded composition.
Note: Since the new runtime does not depend on jQuery anymore, you can try deleting jQuery from your compositions and test them, if you are not using any of the jQuery APIs.
The Edge Animate runtime no longer requires jQuery to run your compositions. However, you can still use a few jQuery APIs that are made available in Edge Animate. For more details, refer to the Edge Animate API reference.
Edge Animate now lets you specify additional file paths to enable you to target required folders for each type of asset while publishing your compositions to Web. Since you can specify a relative path for your assets now, you can share your assets across multiple compositions easily.
The file paths are relative to the target directory. If you type in an absolute file path or use the browse button to target a folder in a different drive (other than that of the target directory), an error is displayed.
In the earlier versions of Edge Animate, when you save a composition, all html, js files and the assets are saved in the same directory. If you save multiple compositions in the one folder, mapping the assets to the respective compositions becomes difficult.
In this release of Edge Animate, the Save As dialog box includes a new option, Save In A Folder, which is selected by default for unsaved compositions. So, by default your compositions are now saved in a separate folder with the name of the composition, along with the related files and assets.
In the Save As dialog box, if you select a folder using your mouse or keyboard, and if the Save In A Folder option is selected, a subfolder is created under the previously selected folder.
To reduce the number of downloads, the preloader DOM is directly included in your composition's HTML. However, if you want the preloader DOM to be a separate js file, enable the option - Publish Preload DOM As A Separate File in Publish Settings as shown below: