What is the difference between MX and spark?

[mikerock]

I want to use MX and spark component with flex. I search on Google but no satisfactory article found. Could give me any idea how to use them. If you try to explain with example, it’s good for me.

[davidkroj]

Have you check adobe website? No worry here i am giving you link of adobe website there mentioned is complete difference in both.http://blogs.adobe.com/JudyGao/2011/04/26/difference-between-mx-formatters-and-spark-formatters/

[joomladeveloper]

The Spark components are new for Flex 4 and are defined in the spark.* packages.

The MX components shipped in previous releases of Flex and are defined in the mx.* packages.
The main differences between Spark and MX components are how you use CSS styles with the components and how you skin them. For the container components, there are additional differences about how the containers perform layout.

Spark and MX define some of the same components. For example, Spark defines a button control in the spark.components package, and MX defines a button control in the mx.controls package. When a component is available in both Spark and MX, Adobe recommends that you use the Spark component.

Spark and MX also define components that are unique. For example, Spark defines components to perform three dimensional effects. MX defines data visualization components, such as the DataGrid and AdvancedDataGrid controls, not included in Spark. Your applications often contains a mixture of Spark and MX components.

[rsewak]

The main differences between Spark and MX components are how you use CSS styles with the components and how you skin them. For the container components, there are additional differences about how the containers perform layout.

[josephlimma]

MX is a more complete and functional set of components for desktop and browser applications, but they had inconsistent skinning rules.
Spark provides more consistent skinning rules, supports right-to-left text, and has touch-enabled components for mobile.

[waqasdhedhi]

mx.formatters are a platform independent classes, it means that once you choose a locale for your application, for example, zh_CN locale, you will get the same display and results on all platforms for Number, date , and others.



spark.formatter are OS dependent classes, which means that the formatted result maybe different on different platforms. This is a big difference between them. If you hope that your application match very well with OS style or look-and-feel, you can think about using spark.formatters, but if you hope that your application can display the uniform results on any platforms, then you can think about using mx.formatters.

[anirban09P]

MX is a more complete and functional set of components for desktop and browser applications, but they had inconsistent skinning rules. The Spark components are new for Flex 4 and are defined in the spark. The MX components shipped in previous releases of Flex and are defined in the MX. Spark and MX define some of the same components. For example, Spark defines a button control in the spark.components package, and MX defines a button control in the MX.controls package.

[stevex]

The Spark components are new for Flex 4 and are defined in the spark.* packages.

The MX components shipped in previous releases of Flex and are defined in the mx.* packages.
The main differences between Spark and MX components are how you use CSS styles with the components and how you skin them. For the container components, there are additional differences about how the containers perform layout.

Spark and MX define some of the same components. For example, Spark defines a button control in the spark.components package, and MX defines a button control in the mx.controls package. When a component is available in both Spark and MX, Adobe recommends that you use the Spark component.

Spark and MX also define components that are unique. For example, Spark defines components to perform three dimensional effects. MX defines data visualization components, such as the DataGrid and AdvancedDataGrid controls, not included in Spark. Your applications often contains a mixture of Spark and MX components.

Thanks for sharing the information.

[webcreations]

MX is an efficient set of elements for pc and web browser applications, but they had unreliable skinning guidelines. Spark gives more consistent skinning guidelines and has touch-enabled elements for mobile. The main differences between Spark and MX components are how you use CSS styles with the components.