September 2008
Intermediate to advanced
660 pages
20h 32m
English
Content preview from Programming Flex 3Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Understanding State Life Cycles
One aspect of states that initially can be confusing is the life cycle of the components within a state. As you learned in Managing Object Creation Policies (Preloading Objects)” earlier in this chapter, by using states you can manage the creation policy for components within the state. By default, all the components in a state are not created until the state is first requested. You also learned that you can control the creation policy such that components are created when the application starts up regardless of whether they belong to the base state, or you can manually create the components in a state. That covers the possibilities for how and when components in states can get created. Next, we need to look at what happens to components once they have been created, because this point can cause a fair amount of confusion if misunderstood.
When a state is set to the current state one of two possible things can happen. If the components in the state have already been created they are immediately added to the display list; if the components haven’t yet been created they are first created and then added to the display list. On the other end of things, when a state is replaced as the current state only one thing can happen: the components that are part of that state are removed from the display list. Once the components in a state have been created, they are not destroyed. Replacing a state as the current state does not destroy the components it contains. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.