Excerpted from Jiujiu Academy
Flex is a presentation server (display service) released by Macromedia. It is an application of java web container or .net server. It generates corresponding .swf files based on .mxml files (pure xml description files and actions scripts), and is transmitted to the client and is explained and executed by the client's flash player or shockwave player, giving users a rich customer experience.
The famous Macromedia Flash is a powerful vector animation editing tool. After starting out as an animation, Flash has been seeking the dominant position of rich internet application (ria rich client). The most influential is that it has launched object-oriented script actions Script2.0, and has established a class library similar to java swing and corresponding component (component). Flex interprets .mxml files through non-Flash channels such as java or .net, and generates corresponding .swf files. Flex's component and flash's component are very similar, but have improved and enhanced.
Using Flash can completely achieve the effect of flex. Why do you still need flex? I understand that there are two reasons: 1. In order to cater to more developers (developers). Flash is born for designers (designers). The interface and the animation concept of flash are incompatible with the developers who write programs. In order to attract more programmers such as jsp/asp/php, Macromedia has launched Flex to use very simple .mxml to describe the interface and uses jsp/asp/php programmers. (x/d)html is very similar, and mxml is more standardized and standardized.
2. For a standard. You must have heard of Microsoft's next-generation system longhorn. At the same time as longhorn is launched, Microsoft will also launch a new language xaml, an interface description language, and the corresponding one is something very similar to smart client and flex. Mxml and Xaml are also very similar... I don't need to mention some of the benefits of this columns.
Flex and j2ee/.net actually have nothing to do with it. Macromedia uses Java to create an application to integrate flash technology into j2ee, and then uses .net technology to create a .net application to integrate flash technology into .net; it should be said that flex solves the most complicated problem in j2ee and .net, which is the problem of the web client. Microsoft is more despicable. Built-in (installed in advance) in IE. It can be called by .net, such as datagrid. Java has no choice but to print it with the most original html tag and tag. It is really a headache. There is also the JavaScript on the client side that is the most difficult to debug, both Java and .net are helpless.
Flex is a presentation server (display service) released by Macromedia. It is an application of java web container or .net server. It generates corresponding .swf files based on .mxml files (pure xml description files and actions scripts), and is transmitted to the client and is explained and executed by the client's flash player or shockwave player, giving users a rich customer experience.
The famous Macromedia Flash is a powerful vector animation editing tool. After starting out as an animation, Flash has been seeking the dominant position of rich internet application (ria rich client). The most influential is that it has launched object-oriented script actions Script2.0, and has established a class library similar to java swing and corresponding component (component). Flex interprets .mxml files through non-Flash channels such as java or .net, and generates corresponding .swf files. Flex's component and flash's component are very similar, but have improved and enhanced.
Using Flash can completely achieve the effect of flex. Why do you still need flex? I understand that there are two reasons: 1. In order to cater to more developers (developers). Flash is born for designers (designers). The interface and the animation concept of flash are incompatible with the developers who write programs. In order to attract more programmers such as jsp/asp/php, Macromedia has launched Flex to use very simple .mxml to describe the interface and uses jsp/asp/php programmers. (x/d)html is very similar, and mxml is more standardized and standardized.
2. For a standard. You must have heard of Microsoft's next-generation system longhorn. At the same time as longhorn is launched, Microsoft will also launch a new language xaml, an interface description language, and the corresponding one is something very similar to smart client and flex. Mxml and Xaml are also very similar... I don't need to mention some of the benefits of this columns.
Flex and j2ee/.net actually have nothing to do with it. Macromedia uses Java to create an application to integrate flash technology into j2ee, and then uses .net technology to create a .net application to integrate flash technology into .net; it should be said that flex solves the most complicated problem in j2ee and .net, which is the problem of the web client. Microsoft is more despicable. Built-in (installed in advance) in IE. It can be called by .net, such as datagrid. Java has no choice but to print it with the most original html tag and tag. It is really a headache. There is also the JavaScript on the client side that is the most difficult to debug, both Java and .net are helpless.