Shulou(Shulou.com)06/02 Report--

This article is to share with you about the misunderstandings of Flex applications. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Ten misunderstandings in Flex Application

1. Use the RIA framework to build Web1.0 applications (new technologies change). One of the challenges in the transition from Web1.0 to RIA comes from a shift in the way you think. Flex gives developers an advanced component library that allows them to accomplish many tasks that were previously impossible. But in many cases, this ability of Flex is ignored, and it is only used to implement more traditional Web1.0 applications. Building a Web2.0 application means more than just local refreshing and rotating rounded icons on the page. For example, Flex developers should use vector graphics to provide users with a visual representation of data and advanced control over the flow of rich applications. Recently StephanJanssen: as a Java developer, learning object-oriented ActionScript and UI markup languages is a piece of cake. But the real challenge for (Java) developers is that we are not designers, and these two technologies are essential for RIA.

two。 Breaking the standard browser experience although Flex does provide an excellent platform to improve the user experience, it is also important to maintain user habits such as back buttons, bookmarks, and autocompletion. Flex3 includes a new deep link feature to support back buttons and bookmarks. You can visit to learn more. There are many components that can be done automatically. You can use components from AdobeExchange.

3. Using too many containers causes Flex applications to slow down. FlashPlayer uses a hierarchical object graph, similar to HTML's document object Model (DOM). The deeper the nesting of the container, the longer it takes to render. There is an article in Adobe's Flex developer Center that discusses the practice of Flex performance, including the details of the use of containers: the performance risk of Flex*** comes from abuse of containers. Nesting too many containers can affect the performance of the application. This is the most serious performance risk faced by Flex developers-but fortunately, it can be completely avoided.

4. Using XML instead of other more optimized protocols slows applications Flex provides developers with a variety of options for data transfer between Flex clients and servers, including AMF3, XML, SOAP, and direct HTTP requests. Ward describes the use and performance of these technologies in his article. For new projects that use Java at the back end, you should consider BlazeDS. BlazeDS is, it uses the AMF3 protocol. AMF is a binary transport protocol, which is easy to integrate with Java, and its performance is better than XML. There are AMF open source implementations for all major back-end technologies. If you do not choose BlazeDS, then you can also choose Hessian. ActionScript/Flex support is provided for binary webservices protocol.

5. Trying to hire Flex developers is hard to find experienced Flex developers these days. Flex is now in the same position as Java in the 1990s. Flex developers are already in short supply. This makes it difficult to find experienced Flex developers. However, this creates a good opportunity for Java developers to expand their skills and work on an emerging and interesting technology. Many companies looking for Flex developers have conducted several weeks of Flex training for Java or other web developers directly, with great success. For developers familiar with Web and GUI programming, learning the Flex language and APIs is easy.

6. Overuse of special effects developers can easily add special effects through Flash. But make sure the special effects are meaningful and match the context. Otherwise, they will only disgust users. The timing of special effects is also important. The interaction designer can help us decide when we should use special effects and when we should not. The interaction designer can also recommend special effects types, intervals, and the most simplified features for us. There is a good article on the use of special effects: most special effects are simply too long. They are not only long, but also slow and even offensive. turn it off. If something like this happens to me, I will turn around and leave, because I really hate this kind of waiting. Don't get me wrong. I'm not against special effects. I just object to special effects that are too long or too much for the purpose. Each special effect can be broken down according to its purpose. Find the purpose of the special effect you want, and then use it.

7. Without building an enterprise ecosystem, like other software projects, it is important to build an enterprise ecosystem for your Flex application. Test-driven development (TDD) is currently the solution for most enterprise projects. For Flex, the framework can be used to write unit tests. On Adobe's developer network,. In addition, it can be used to measure code coverage. Continuous integration () has proved to be a good practice when multiple developers work together. Similar to Java applications, there are Ant and Maven plug-ins for continuous integration of your Flex applications.

8. Not using the entire framework there are a lot of optional features in AdobeFlex, and you should consider using them in your Flex application. For example, run-time shared libraries (i.e., RSL) can be used to reduce the size of applications. You can integrate shared resources into separate files so that they can be downloaded and cached separately on the client side, reducing the size of SWF files generated by the application. Many Flex applications can load these shared resources at run time, but each client only needs to download it once. These shared resources are called runtime shared libraries (RuntimeSharedLibraries). Another feature of the framework is built-in accessibility. You can learn more about the accessibility of Flex. In addition to built-in accessibility, the framework also provides built-in support for localization. Visit to learn about the Flex3 framework features of * *.

9. Using a complex renderer to slow down DateGrid has been well optimized for DataGrid's out-of-the-box itemRenderer. Misunderstanding # 3 discusses the performance of containers that are too deeply nested. One place in Flex that can easily lead to deep nesting of containers is DataGrid's item renderer. The number of item renderers rendered by DataGrid is equal to the number of visible rows multiplied by the number of visible columns. The custom DataGrid and Listitem renderers should be very well optimized. When you need to use complex layout logic in the item renderer, * uses UIComponent (or other underlying classes) and manually locates the contents of the cell.

10. No offline applications are prepared. The traditional model of RIAs is the browser. However, technologies like and this allow applications to run offline. If users need to be able to apply offline to Flex and you are not ready, it will be extremely difficult to change your application to support offline features. Typically, in web applications, business logic exists on the server side. In an offline RIAs, the business logic must go to the client. In order to make the application support both offline and online, it is necessary to determine the location of some business logic in advance.

Thank you for reading! This is the end of this article on "what are the misunderstandings of Flex applications?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.