Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I would suggest writing this application using Flex. Mainly because the Flex toolchain is <em>a lot</em> better than Flash Professional in my opinion. While there's nothing in your question that really seem to require the Flex framework, you would probably benefit from using it. Not only for its superior development environment but also because there's a few things in the Flex framework that just makes working with data a whole lot easier.</p> <p>Regardless, there seems to be a lot of confusion regarding terminology here, so I'll try to clear a few things up:</p> <p><strong>DISCLAIMER</strong>: This is by no means a comprehensive list of everything flash. While I've tried my best to be factual I quite possibly have left out some important details for the sake of brevity (hey, at least I tried) and in other cases I may simply be wrong. The usual caveats about considering the source apply.</p> <ul> <li><p><strong>Flash player</strong>, provides the ability to render vector and raster graphics as well as run user code in a virtual machine. The player is the core of the flash platform, enabling content to run on multiple platforms (generally without any platform specific modifications.) There are quite a few APIs in the player that are actually native code but can be called from ActionScript.</p></li> <li><p><strong>ActionScript</strong> is the high level language of choice for the Flash Platform. There are others, most notably <a href="http://haxe.org/" rel="noreferrer">haXe</a>, but they aren't supported by Adobe's tools. There are three versions of the language: ActionScript 1, 2 and 3. The first two were used prior to Flash 9, which introduced a completely rewritten virtual machine (AVM2) and thus also introduced AS3. The former languages run in an older virtual machine called AVM1. Older content produced for AVM1 can run in newer AVM2 enabled players. They will still run in AVM1 mode however, in order to retain backwards compatibility. Flash actually handles backwards compatibility remarkably well.</p></li> <li><p><strong>Flash Professional</strong>, also known as the Flash IDE, is the name of a tool to produce flash content. It started out as a way to just create animations, but as the flash movie format got scripting capabilities, so did the tool. However, the scripting have long been a bastard child of this tool. While the past couple of versions have seen improvements in this area it still pales in comparison with other more developer centric environments. This tool only compiles pure ActionScript projects, is not used to develop Flex applications and is generally considered to be more designer friendly than developer friendly.</p></li> <li><p><strong>Flex</strong> is the name of Adobe's enterprise application framework. There are a few key technologies to Flex and it's more than just a core library of functionality. I'll try to concisely explain the key technologies of the framework below. The Flex SDK is actually open source and can be used freely to develop applications. However, while it contains anything needed to build Flex applications, it doesn't actually include an IDE.</p> <ul> <li><p><strong>MXML</strong> is a declarative language. It is generally used to declaratively define views, but can be used for many things. For instance, the <a href="http://swizframework.org/" rel="noreferrer">swiz framework</a> leverage MXML to declaratively define dependencies using <a href="http://en.wikipedia.org/wiki/Inversion_of_control" rel="noreferrer">IoC</a>. There's of course a lot more to swiz, but that's beyond the scope of this answer.</p></li> <li><p><strong>MXMLC &amp; COMPC</strong> are two compilers used to compile flex projects. The former is used to compile swf applications, the latter is used to compile swc libraries.</p></li> <li><p><strong>The core library</strong> among other things includes two standard component sets: MX and Spark; the former often referred to as Halo. MX is an older component set and while still supported, is considered deprecated and will likely be phased out once Spark reaches feature parity with MX. The two component sets are largely compatible with each other however and can co-exist quite well in the same application. Other notable functionality provided is quite comprehensive data access and management functionality, both for text based data such as XML or JSON as well as binary data (AMF.)</p> <p>The library is commonly referred to as just <strong>Flex</strong> or the <strong>Flex framework</strong>.</p></li> </ul></li> <li><p><strong>Flash Builder</strong> is Adobe's IDE for the development of Flex applications. While it is certainly possible to use it to develop pure AS3 applications it's most commonly used to develop Flex applications. It's a decent IDE with most of the features available in a modern development environment, but there are popular alternatives such as <a href="http://www.fdt.powerflasher.com/developer-tools/fdt/home/" rel="noreferrer">PowerFlasher's FDT</a>. While the Flex SDK is free and open source, Flash Builder is both proprietary and commercial software.</p></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload