What is mx_internal?
Well the best explanation is: “mx_internal is a namespace used by the Flex framework to partition out functions and properties that may change in future releases of the Flex SDK.”.
Related links:
Which Flex Framework is best?
There are a number of flex frameworks available for MVC Architecture Framework implementation of Flex Applications, like Cairngorm, PureMVC and Mate etc. Which one to use? Here is a interesting thread for it. Please click here to see the discussion thread.
What is Mate?
Mate is a tag-based, event-driven Flex framework.
Flex applications are event-driven. Mate framework has been created to make it easy to handle the events your Flex application creates. Mate allows you to define who is handling those events, whether data needs to be retrieved from the server, or other events need to be triggered.
In addition, Mate provides a mechanism for dependency injection to make it easy for the different parts of your application to get the data and objects they need.
For more information, Please follow the link.
What is Cairngorm?
Cairngorm is a resource provided by the Adobe Technical Services Organisation to developers and technical architects to deliver successful Flex projects in the enterprise.In addition to the guidelines, Cairngorm provides tools and libraries for building applications that apply a form of the Model-View-Controller (MVC) pattern. The tools help to ensure efficient and high-quality delivery of Flex applications, while the libraries solve recurring problems in Rich Internet Applications.
Click here for more informations.
What is BlazeDS?
BlazeDS is the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Adobe® Flex™ and Adobe AIR™ applications for more responsive rich Internet application (RIA) experiences.
Related Links:
What is AMF?
AMF in short for Action Message Format, is a binary format for exchanging data. It is most commonly used to transfer data between a Flash or Flex application and a database via a remoting request. In a remoting call, the external elements being called would be application tier services, which would likely be running on an application server such as Adobe ColdFusion, Java, PHP, or .NET.
Related Links:
What are Modules?
Flex Modules are code functionality compiled to dynamically-loadable SWF files that can be loaded and unloaded by an application at run-time.
Modules let you split your application into several pieces, or modules. The main application, or loader, can dynamically load other modules that it requires, when it needs them. It does not have to load all modules when it starts, nor does it have to load any modules if the user does not interact with them.
Any number of applications can share a module, but a module cannot be run by itself, independently of an application.
Related links:
What is Runtime Shared Libraries?
One way to reduce the size of your applications’ SWF files is by externalizing shared assets into stand-alone files that can be separately downloaded and cached on the client. These shared assets can be loaded and used by any number of applications at run time, but must be transferred only once to the client. These shared files are known as Runtime Shared Libraries or RSLs.
Click here for more informations.
What is difference between MXML and ActionScript?
When you learn Flex there is often confusion between what MXML is and how it relates to ActionScript. We tend to think of it as different entities, but the reality is MXML is just an abstracted form of ActionScript. MXML is a declarative XML syntax that is converted by the compiler into an ActionScript class. This is an important concept to understand because this is the root of why the compiler throws an error when trying to have a MXML file and an ActionScript File with the same name in the same package. The MXML file is really just an ActionScript class and therefore we have a conflicting namespace error.
To help visualize this, imagine the root node of the MXML file is the same as an extends statement. When we use
something like this in MyFirstApp.mxml:
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"> ... </mx:Application>
Means we are saying:
ublic class MyFirstApp extends Application
So why do we need MXML syntax if it just becomes ActionScript. As you are probably well aware, doing complex layout in ActionScript takes a ton of code, especially when you get into the world of nested layout. It can be done in code but why would you want to? XML is all about parent/child hierarchies and by using this as a layout language you can quickly define complex organizational structures that would have taken hundreds of lines of code if you did it all in ActionScript.
How to communicate between Flex and JavaScript?
For communication between Flex and JavaScript we need the ExternalInterface class.
| Method | Defined By | ||
|---|---|---|---|
|
addCallback(functionName:String, closure:Function):void
[static] Registers an ActionScript method as callable from the container.
|
ExternalInterface | ||
|
call(functionName:String, … arguments):*
[static] Calls a function exposed by the SWF container, passing zero or more arguments.
|
ExternalInterface | ||
Click here for more details.