Catálogo de publicaciones - libros

This chapter concludes the third and last part of the book.

After reading the book from cover to cover, you can now enjoy a high degree of control over the component architecture and its standard components and start implementing your own component-based applications in Flash.

Hopefully, this book has shown you that components can be used conveniently to produce powerful applications in a fraction of the time that would be required to develop the same applications without using them.

A software developer knows that there always is a lot of work to do, but also knows how to have fun doing it.

Enjoy your experiments and your next projects.

After reading this chapter, you will be aware of which components have been included in the Flash Component Architecture and what functionality they provide.

You have also found a tool (the Reusability Card) that will tell you at a glance how reusable a component actually is.

You may well consult this chapter again when deciding what components to use in your next project.

In the next chapter, we are going to examine the many options offered by the architecture to efficiently integrate different component instances into a robust component-based application.

After reading this chapter, you will be aware of which components have been included in the Flash Component Architecture and what functionality they provide.

You have also found a tool (the Reusability Card) that will tell you at a glance how reusable a component actually is.

You may well consult this chapter again when deciding what components to use in your next project.

In the next chapter, we are going to examine the many options offered by the architecture to efficiently integrate different component instances into a robust component-based application.

After reading this chapter, you will be aware of which components have been included in the Flash Component Architecture and what functionality they provide.

You have also found a tool (the Reusability Card) that will tell you at a glance how reusable a component actually is.

You may well consult this chapter again when deciding what components to use in your next project.

In the next chapter, we are going to examine the many options offered by the architecture to efficiently integrate different component instances into a robust component-based application.

In this chapter, you have learned how the component architecture implements styles and skins.

You have also learned that there are three different kind of skins, and that for some of them the separation of code from representation cannot be achieved, because in several cases a skin’s appearance is defined also, or exclusively, by ActionScript code.

You became aware of a set of different techniques that allow you to overcome any limitation you may encounter when customizing a component.

The approaches presented here can be applied in many different situations. The third part of the book, starting next, exploits the application of these techniques in the context of each standard component, providing plenty of concrete and different examples.

In this chapter, you have learned how the component architecture implements styles and skins.

You have also learned that there are three different kind of skins, and that for some of them the separation of code from representation cannot be achieved, because in several cases a skin’s appearance is defined also, or exclusively, by ActionScript code.

You became aware of a set of different techniques that allow you to overcome any limitation you may encounter when customizing a component.

The approaches presented here can be applied in many different situations. The third part of the book, starting next, exploits the application of these techniques in the context of each standard component, providing plenty of concrete and different examples.

In this chapter, you learned how to save a lot of time when it comes to writing XML parsing code.

Such a result is achieved by realizing that most of the time spent writing code to access the content of XML documents goes into translating the generic XML DOM supported by the XML class into an object model that is specific to your application.

You also learned how to use the XModel class—a huge time-saver since

The next chapter will complete the second part of the book dedicated to mastering the techniques for exploiting the component architecture by introducing the customization process.

This chapter concludes the third and last part of the book.

After reading the book from cover to cover, you can now enjoy a high degree of control over the component architecture and its standard components and start implementing your own component-based applications in Flash.

Hopefully, this book has shown you that components can be used conveniently to produce powerful applications in a fraction of the time that would be required to develop the same applications without using them.

A software developer knows that there always is a lot of work to do, but also knows how to have fun doing it.

Enjoy your experiments and your next projects.

After reading this chapter, you will be aware of which components have been included in the Flash Component Architecture and what functionality they provide.

You have also found a tool (the Reusability Card) that will tell you at a glance how reusable a component actually is.

You may well consult this chapter again when deciding what components to use in your next project.

In the next chapter, we are going to examine the many options offered by the architecture to efficiently integrate different component instances into a robust component-based application.

In this chapter, you learned how to save a lot of time when it comes to writing XML parsing code.

Such a result is achieved by realizing that most of the time spent writing code to access the content of XML documents goes into translating the generic XML DOM supported by the XML class into an object model that is specific to your application.

You also learned how to use the XModel class—a huge time-saver since

The next chapter will complete the second part of the book dedicated to mastering the techniques for exploiting the component architecture by introducing the customization process.