Adobe Flex 4.5 开发英文指南

需积分: 10 159 浏览量更新于2024-07-27 1 收藏 33.92MB PDF 举报

"Adobe Flex 4.5英文帮助文档提供了全面的开发指南，适用于有一定英语基础和Flex开发经验的专业人士。这份文档详细介绍了Flex 4.5的主要特性、开发流程和应用架构，以及构建用户界面的方法。" 在《Flex 4.5 Introduction》章节中，开发者可以了解到开始使用Flex 4.5的基础知识，包括如何从早期版本迁移至Flex 4.5，这涉及到API的变化、新功能的引入和代码优化策略。在《Getting started》章节，文档深入探讨了使用MXML和ActionScript开发应用程序的方法。MXML是一种声明式语言，用于快速创建用户界面，而ActionScript则提供编程逻辑支持。本章还涵盖了MXML的语法结构和ActionScript的基本用法，以及事件处理的机制。在《Application architecture》章节，开发者将学习到应用开发的不同阶段，包括设计、实现和部署。此外，本章讨论了应用程序的结构，如组件、服务和数据的组织方式，以及安全性的考量，如沙箱模型和跨域策略。模块化应用程序的开发也在此部分得到详述，讲解了如何设计和加载子应用程序，以及如何利用FlexAjaxBridge与JavaScript进行交互。在《Building the user interface》章节中，文档详细阐述了Flex 4.5的可视化组件，包括各种预定义的UI组件，如按钮、文本框等。数据绑定的概念被引入，使得数据和界面元素之间能自动保持同步。容器的使用是构建复杂布局的关键，文档介绍了两种主要的容器类型：Spark和MX容器，以及它们各自的特点和布局策略。此外，自定义Spark ItemRenderers和基于列表的控件（如List、DataGrid）的使用方法也被涵盖。这份Adobe Flex 4.5的英文帮助文档为开发者提供了深入理解Flex框架、高效开发RIA（富互联网应用）所需的所有信息。虽然它是英文版，但对于有一定英语基础的开发人员来说，它无疑是一份宝贵的参考资料，可以帮助他们充分利用Flex 4.5的功能来提升应用的用户体验和性能。

USING FLEX 4.5

Getting started

Last updated 9/8/2011

XML namespaces give you the ability to use classes in custom packages that are not in the Flex namespaces. The

following example shows an application that contains a custom component called CustomBox. The namespace value

myComponents.boxes.* indicates that an MXML component called CustomBox is in the myComponents/boxes

directory.

<?xml version="1.0"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:mx="library://ns.adobe.com/flex/mx"

xmlns:s="library://ns.adobe.com/flex/spark"

xmlns:MyComps="myComponents.boxes.*">

<s:Panel title="My Application"

height="150">

<MyComps:CustomBox/>

</s:Panel>

</s:Application>

The myComponents/boxes directory can be a subdirectory of the directory that contains the application file, or it can

be a subdirectory of one of the ActionScript source path directories assigned in the flex-config.xml file. If copies of the

same file exist in both places, Flex uses the file in the application file directory. The prefix name is arbitrary, but it must

be used as declared.

When using a component contained in a SWC file, the package name and the namespace must match, even though

the SWC file is in the same directory as the MXML file that uses it. A SWC file is an archive file for Flex components.

SWC files make it easy to exchange components among Flex developers. You exchange only a single file, rather than

the MXML or ActionScript files and images, along with other resource files. Also, the SWF file inside a SWC file is

compiled, which means that the source code is obfuscated from casual view.

For more information on SWC files, see “Flex compilers” on page 2163.

Using MXML to trigger run-time code

Flex applications are driven by run-time events, such as when a user selects a Button control. You can specify event

listeners, which consist of code for handling run-time events, in the event properties of MXML tags. For example, the

<s:Button> tag has a click event property in which you can specify ActionScript code that executes when the Button

control is clicked at run time. You can specify simple event listener code directly in event properties. To use more

complex code, you can specify the name of an ActionScript function defined in an

<fx:Script> tag.

The following example shows an application that contains a Button control and a TextArea control. The click

property of the Button control contains a simple event listener that sets the value of the TextArea control’s

text

property to the text

Hello World.

Effect classes mx.effects.Parallel

mx.effects.Sequence

mx.states.Transition

mx.effects.Wait

States classes mx.states.State

mx.states.AddItems

Component classes mx.controls.Spacer

mx.controls.SWFLoader

Category Class

USING FLEX 4.5

Getting started

Last updated 9/8/2011

<?xml version="1.0"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:mx="library://ns.adobe.com/flex/mx"

xmlns:s="library://ns.adobe.com/flex/spark">

<s:Panel title="My Application">

<s:VGroup left="10" right="10" top="10" bottom="10">

<s:Label text="Enter Text:"/>

<s:TextInput id="textinput1"

text="Hello"/>

<s:Label text="Bind Text to the TextArea control:"/>

<s:TextArea id="textarea1"

text="{textinput1.text}"/>

<s:Button label="Submit"

click="textinput1.text='Goodbye';"/>

</s:VGroup>

</s:Panel>

</s:Application>

As an alternative to the curly braces ({ }) syntax, you can use the <fx:Binding> tag, in which you specify the source

and destination of a binding. For more information about data binding, see

“Data binding” on page 298.

Using RPC services

Remote-procedure-call (RPC) services let your application interact with remote servers to provide data to your

applications, or for your application to send data to a server.

Flex is designed to interact with several types of RPC services that provide access to local and remote server-side logic.

For example, a Flex application can connect to a web service that uses the Simple Object Access Protocol (SOAP), a

Java object residing on the same application server as Flex using AMF, or an HTTP URL that returns XML.

The MXML components that provide data access are called RPC components. MXML includes the following types of

RPC components:

• WebService provides access to SOAP-based web services.

• HTTPService provides access to HTTP URLs that return data.

• RemoteObject provides access to Java objects using the AMF protocol (Adobe LiveCycle Data Services ES only).

In MXML, define the RPC components in an <fx:Declarations> tag. You use the <fx:Declarations> tag to

declare non-visual components an MXML file.

The following example shows an application that calls a web service that provides weather information, and displays

the current temperature for a given ZIP code. The application binds the ZIP code that a user enters in a TextInput

control to a web service input parameter. It binds the current temperature value contained in the web service result to

a TextArea control.

USING FLEX 4.5

Getting started

Last updated 9/8/2011

<?xml version="1.0"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:mx="library://ns.adobe.com/flex/mx"

xmlns:s="library://ns.adobe.com/flex/spark">

<fx:Declarations>

<!-- Define the web service connection

(the specified WSDL URL is not functional). -->

<s:WebService id="WeatherService"

wsdl="http:/example.com/ws/WeatherService?wsdl"

useProxy="false">

<!-- Bind the value of the ZIP code entered in the TextInput control

to the ZipCode parameter of the GetWeather operation. -->

<s:operation name="GetWeather">

<s:request>

</s:request>

</s:operation>

</s:WebService>

</fx:Declarations>

<s:Panel title="My Application">

<s:VGroup left="10" right="10" top="10" bottom="10">

<s:TextInput id="zip" width="200" text="Zipcode please?"/>

<s:Button width="60" label="Get Weather"

click="WeatherService.GetWeather.send();"/>

<s:Label text="Location:"/>

<s:TextArea text="{WeatherService.GetWeather.lastResult.Location}"/>

<s:Label text="Temperature:"/>

<s:TextArea

text="{WeatherService.GetWeather.lastResult.CurrentTemp}"/>

</s:VGroup>

</s:Panel>

</s:Application>

For more information about using RPC services, see Accessing Server-Side Data with Flex.

Storing data in a data model

You can use a data model to store application-specific data. A data model is an ActionScript object that provides

properties for storing data, and optionally contains methods for additional functionality. Data models provide a way

to store data in the Flex application before it is sent to the server, or to store data sent from the server before using it

in the application.

You can declare a simple data model that does not require methods in an <fx:Model>, <fx:XML>, or <fx:XMLList>

tag. In MXML, define a data model in an

<fx:Declarations> tag. You use the <fx:Declarations> tag to declare

non-visual components an MXML file.

The following example shows an application that contains TextInput controls for entering personal contact

information and a data model, represented by the

<fx:Model> tag, for storing the contact information:

USING FLEX 4.5

Getting started

Last updated 9/8/2011

<?xml version="1.0"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:mx="library://ns.adobe.com/flex/mx"

xmlns:s="library://ns.adobe.com/flex/spark">

<fx:Declarations>

<!-- A data model called "contact" stores contact information.

The text property of each TextInput control shown above

is passed to a field of the data model by using data binding. -->

<fx:Model id="contact">

<info>

<homePhone>{homePhoneInput.text}</homePhone>

<cellPhone>{cellPhoneInput.text}</cellPhone>

<email>{emailInput.text}</email>

</info>

</fx:Model>

</fx:Declarations>

<s:Panel title="My Application">

<s:VGroup left="10" right="10" top="10" bottom="10">

<s:TextInput id="homePhoneInput"

text="This isn't a valid phone number."/>

<s:TextInput id="cellPhoneInput"

text="(999)999-999"/>

<s:TextInput id="emailInput"

text="me@somewhere.net"/>

</s:VGroup>

</s:Panel>

</s:Application>

This example uses data binding in the model definition to automatically copy data from the UI controls to the data

model.

Validating data

Flex includes a set of standard validator components for data such as phone numbers, social security numbers, and

ZIP codes. You can also create your own custom validator.

In MXML, define validators in an <fx:Declarations> tag. You use the <fx:Declarations> tag to declare non-

visual components an MXML file.

The following example uses validator components for validating that the expected type of data is entered in the

TextInput fields. In this example, you validate a phone number by using the PhoneNumberValidator class and an e-

mail address by using the EmailValidator class. Validation is triggered automatically when the user edits a TextInput

control. If validation fails, the user receives immediate visual feedback.

剩余2576页未读，继续阅读

chandler_guo

粉丝: 0
资源: 6

Adobe Flex 4.5 开发英文指南

Flex中文帮助文档（含4份.PDF文档）

汉化 Flex Builder 3 帮助文档

Flex中文帮助文档4章

flex中文帮助文档chm格式(精品)

FLEX中文帮助PDF文档

Flex Builder3.0 帮助文档

flex3.0 中文帮助文档

Flex 3实用英文帮助文档及实例程序

FLEX开发中文文档

flex性能优化文档

最新资源