Adobe Flex 4.6 开发指南

需积分: 9 168 浏览量更新于2024-07-18 收藏 33.91MB PDF 举报

"Adobe Flex 4.6 帮助文档" Adobe Flex 4.6 是一个软件开发工具包(SDK)，包含了Flex框架（组件类库）和Flex编译器，允许开发者使用自选的集成开发环境(IDE)自由地开发和部署Flex应用程序。这个文档是针对Flex 4.6的介绍和指南，适用于想要学习或迁移至Flex 4.6的开发者。第一章：Flex 4.6简介这一章介绍了Flex 4.6的基本概念，包括如何开始使用Flex 4.6以及为开发者提供的各种工具。其中提到了开发工具对Flex 4.6的支持，以及关于从先前版本迁移至Flex 4.6的相关信息。第二章：开始开发在这一部分，开发者将了解到如何使用MXML进行应用开发。MXML是一种声明式语言，用于构建Flex界面。章节深入讨论了MXML的语法，同时介绍了ActionScript的使用，这是Flex中的主要编程语言。此外，还涵盖了事件处理和SDK配置。第三章：应用架构本章关注应用的开发阶段、结构和安全。它详细阐述了应用的生命周期，从设计到实现的各个步骤。此外，还涉及了应用的安全策略，模块化应用的构建，如何加载子应用程序，以及FlexAjaxBridge，它允许Flex应用与JavaScript进行交互。最后，还提到了运行时共享库(RSLs)的概念。第四章：构建用户界面这一章是关于创建吸引人的和功能丰富的用户界面。它详细介绍了视觉组件，数据绑定，容器的使用，包括布局管理器。Flex提供了两种主要的容器类型：Spark和MX。Spark容器包括自定义项渲染器，列表基础控件，以及数据网格控件。而MX容器则涵盖了一系列传统的布局容器。通过以上内容，开发者可以全面了解Flex 4.6的开发环境，掌握从设计、编码到构建用户界面的全过程，并能深入理解Flex 4.6的架构和组件系统，从而高效地开发富互联网应用程序。

USING FLEX

Getting started

Last updated 9/25/2015

Category Class

RPC classes mx.messaging.channels.AMFChannel

mx.rpc.CallResponder

mx.messaging.ChannelSet

mx.messaging.Consumer

mx.messaging.channels.HTTPChannel

mx.rpc.http.mxml.HTTPService

mx.messaging.Producer

mx.rpc.remoting.mxml.RemoteObject

mx.rpc.remoting.mxml.Operation

mx.messaging.channels.RTMPChannel

mx.messaging.channels.SecureAMFChannel

mx.messaging.channels.SecureStreamingAMFChannel

mx.messaging.channels.SecureHTTPChannel

mx.messaging.channels.SecureStreamingHTTPChannel

mx.messaging.channels.SecureRTMPChannel

mx.messaging.channels.StreamingAMFChannel

mx.messaging.channels.StreamingHTTPChannel

mx.rpc.soap.mxml.WebService

mx.rpc.soap.mxml.Operation

mx.data.mxml.DataService

Graphics classes mx.graphics.BitmapFill

mx.geom.CompoundTransform

mx.graphics.GradientEntry

mx.graphics.LinearGradient

mx.graphics.LinearGradientStroke

mx.graphics.RadialGradient

mx.graphics.RadialGradientStroke

mx.graphics.SolidColor

mx.graphics.SolidColorStroke

mx.graphics.Stroke

mx.geom.Transform

USING FLEX

Getting started

Last updated 9/25/2015

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 2164.

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

Getting started

Last updated 9/25/2015

<?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 299.

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

Getting started

Last updated 9/25/2015

<?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:

剩余2574页未读，继续阅读

键盘王者

粉丝: 9
资源: 2

Adobe Flex 4.6 开发指南

flex开发技术文档

flex api的帮助文档

FLEX4.0开发文档

Adobe Flex 4.6 官方文档详解

Flex 4.6文档

flex4.6文档

flex4.6文档学习资料

flex 4.6 4.5 的api 文档.part1

Flex4.6 API

Flex 4.6 官方英文帮助文档详解：从入门到架构设计

最新资源