parsley2.4英文开发手册

1 Overview

Parsley is an Application Framework for Flex and Flash Applications built upon an IOC Container and Messaging

Framework that can be used to create highly decoupled architectures. It allows you to configure objects to be managed

by the container with Metadata, MXML, XML or ActionScript and is easily extensible.

While many other Application Frameworks for the Flash Platform are either a pure Flex Framework that cannot be used

without the Flex SDK or are a classic Flash Framework without any deeper integration with Flex, Parsley is both. The

core of the framework (the IOC Container and the Messaging Subsystem) does not depend on the Flex SDK at all, but

there are several additional modules that are specifically designed for Flex, providing support for MXML Configuration,

View Wiring and Flex Modules.

frameworks for simple applications, it also provides many features which are essential for building large, complex and

modular applications, like support for Flex Modules, Object Disposal or numerous extension points.

Dependency Injection

The core feature of any IOC Container. Now with Parsley 2 dependencies can be conveniently declared using AS3

Metadata Tags ([Inject]) on properties, methods or constructors or alternatively with MXML or XML. See

4

Dependency

Injection for details.

Messaging

Parsley contains a Messaging Framework that allows for objects to send and receive messages in a fully decoupled way.

You can declare events on sending objects with the [ManagedEvents] tags, so that they will be routed through Parsley

Advanced IOC Container Features

6.5

Context

Lifecycle: Objects can have methods marked with [PostConstruct] (which will be invoked after the

object has been instantiated and configured) or [PreDestroy] which will be invoked when the container gets destroyed.

For modular applications it's essential that you can create dynamically loaded sub-contexts and be able to dispose the

whole module when it's no longer needed by the application.

6.2 Asynchronous Object Initialization: Configuration option for asynchronously initializing objects (e.g. objects that

need to load data before they can operate). In this case the container will defer the initialization of other objects until

those configured to be asynchronous are ready.

Flex View Wiring

Module, containing services, actions, mediators and so on, which are only needed for a particular context. The whole

sub-context gets automatically destroyed, disposing all objects configured for the module, when the Flex Module gets

unloaded. See 8 Using Flex Modules for details.

Localization

Allows to bind properties to resources with the [ResourceBinding] tag. Integrates with the Flex ResourceManager for

Flex Applications and contains its own Localization Module for Flash Applications. See 10

Localization for details.

Extensibility

Parsley can serve as the base for building higher-level frameworks on top of. Or you may just want to create some

additional configuration tags for use cases which are frequent for a particular application. Parsley is easy to extend. A

into a single large SWC (for both frameworks one SWC for Flex and one for Flash).

Alternatively the module folder contains smaller SWCs only containing a single framework module which can be

combined to add only the feature set required by your application to the classpath. To use these smaller module SWCs

it's essential to know the dependencies and the content of each SWC.

The following diagram shows the dependencies between the various SWCs. The names correspond to the names of the

SWCs minus version number and suffix. Several optional dependencies were left out to keep the diagram clear. Most of

them are obvious (e.g. several modules include custom XML configuration tags and in case you use those the module

will also depend on parsley-xml).

The following table summarizes the content for each of these SWCs:

1.3 Other resources

In addition to the material presented in this manual there are also some articles and sample applications available

which have been created by other users. If you have created something that you want to see listed here just post a link

in the Forum.

2 Getting Started

This chapter gives a very quick introduction on how to build an application with Parsley, linking to other parts of the

manual for more detailed descriptions. Most of the explanations apply in the same way to building Flex or Flash

Applications. Examples that only apply for Flex development will be pointed out accordingly.

2.1 Adding the Framework SWCs

To start working with Parsley you need to add several of its SWCs to your classpath first. Which ones you'll need

depends on the feature set you'll be using and whether you'll be building a Flex or Flash Application.

The quickest way to get started is to add the SWCs that contain the whole framework. You'll find them in the release

folder of the download Zip.

Required SWCs for Flex Applications

you'd need to know the content and the dependencies for those SWCs, which is described in 1.2 Parsley and Spicelib

Module SWCs.

2.2 Defining Object Dependencies

This is probably the most frequently used feature of Parsley. Defining dependencies is a lot more convenient since

Parsley 2 where we introduced configuration with Metadata or MXML in addition to XML files.

Using the [Inject] metadata tag

You can use the tag on properties:

Or you can use it on methods to declare multiple dependencies at once:

The nice thing in the example above is that Parsley will also reflect on the parameter types and treat optional

parameters as optional dependencies. So in this example the container will throw an Error if the LoginService is

public function set loginService (service:LoginService) : void {

[Inject]

public function init (loginService:LoginService, cartService:CartService = null) : void {