In Flex terminology, a state is a collection of changes (called overrides) to a view. The overrides can comprise additions or removals of components as well as changes to their properties and behaviors. Every Flex application has at least one state, referred to as its base state. Flex states enable you to more easily change the view for an application, whether at a macro or a micro level. For example, you can define two states that act as screens in an application (e.g., a login screen and a menu screen). Using states for screens is an example of a macro-level use. At the micro level, you can use states to manage cascading forms and even different views for components (e.g., rollover changes).
The Flex framework provides an entire library for states and state management. You can create and manage states from MXML or ActionScript. Furthermore, you can use states in conjunction with other Flex features, such as transitions and history management, to create robust, responsive, and engaging applications and user interfaces with relative ease. In this chapter, you'll learn how to work with Flex states.
The four strangers had lost some of their earlier mystery as their opinions began to unfold. When Kip returned, Pete said, “Kip, I’ve been thinking about our incentive plans, and I’ve got to tell you that I agree with Yolanda. For at least some of my people, the pay-for-performance plans have worked well. In fact, one or two of my salespeople earn more than I do.” Lucy laughed, and Kip seemed sincerely interested in Pete’s point. Yolanda, on the other hand, had been burnt before by these three and was sitting in a more wait-and-see posture.
“There are always individuals in any organization, public or private, who possess hard-wired advantages like intelligence, charm, or cunning to exploit these programs,” Kip granted. “They’re able to make virtually any incentive program work to their advantage. These individuals consistently win the contests and earn the incentive pay that seems to elude their peers. Proponents of incentive pay plans argue that money motivates! And they’re right—but only to a point.”
“Life isn't about how to survive the storm, but how to dance in the rain”
Resilience is all about positive engagement with adversity and sustaining competence with consistency when under stress. It is about accessing the range of emotions being experienced, rather than denial. It is about learning to put attention on to positive emotions and to buffer the self from being overwhelmed by painful ones. Counsellors and supervisors take it for granted that they will be working in a context of high, even occasionally overwhelming, emotional demands. These demands can have an overwhelming quality because it is difficult to control the quantity of approaches from clients or supervisees on any one day in work settings designed to be responsive to needs. But that is not all. The quality of the interaction is very often draining, as people who are stuck, scared, angry, sad, or in pain come for aid. It is a truism that those of us who are drawn to work as therapists have our own shadow and pain to address as an important part of becoming and remaining able to do this work. I am interested in describing the supervisor's role with counsellors who are vulnerable, or might become stressed. I call on the wounded healer archetype explored further in the next chapter while discussing how to support and sustain maximum resilience through supervision that enables counsellors to stay in touch with self-esteem and make good use of this external social support.
Ishall dedicate this last chapter, predictably, to the final pages of “Subversion of the subject …”. The title I propose to you as a framework for our work is “The castration complex in Lacan’s teaching”.
This outline will be supported, as has been the case during this course, by a series of quotations. The first one has already been presented to you during the last class:
But it is not the Law itself that bars the subject’s access to jouissance—rather it creates out of an almost natural barrier a barred subject. For it is pleasure that sets the limits on jouissance, pleasure as that which binds incoherent life together,1 until another, unchallengeable prohibition arises from the regulation that Freud discovered as the primary process and appropriate law of pleasure.
It has been said that in this discovery Freud merely followed the course already being pursued by the science of his time, indeed, that it belonged to a long-standing tradition. To appreciate the true audacity of his step, we have only to consider hisrecompense, which was not slow in coming: failure over the heteroclite nature of the castration complex (pp. 352–353).
Active Record, which controls the interaction between your application and the database, is the heart of Rails. Active Record's elegant simplicity almost completely eliminates the need for configuration; in this chapter, you'll see how Active Record's conventions reduce your configuration from hundreds of lines to a handful. You'll also see how Active Record's metaprogramming dynamically adds capabilities to your classes, based on the contents and structure of the database. Finally, you'll use Active Record's elegant extensions of Ruby to quickly validate your code with less effort than ever before.
Martin Fowler cataloged the Active Record design pattern in a book called Patterns of Enterprise Architecture.[*] The Rails framework is an implementation of that idea. With any Active Record implementation, users manipulate database tables through record objects. Each record represents a row in a database table, and each Active Record object has CRUD (Create, Read, Update, and Delete) methods for database access. This strategy allows simple designs and straightforward mappings between database tables and application objects.