The Tree component is used to represent a hierarchical data set, providing an interface for the user to drill down through the hierarchy in order to select an atomic element as below:

When using XML as the data source for a Tree, you should use the labelField property to identify what in the data source should be used for the label. The XML data source is being defined inline and has generic element names. But its tag attributes, referred to using @tag, will be used as the labels in the Tree. You can follow the source code I share to see what happen. Another important property is showRoot. In the following code, you couldn’t see the “ROOT” of tree, because I set showRoot=false. (If you don’t like it, you can delete it. The default value of showRoot is true). I hope you enjoy this short article and have fun with flex 4.

Source code:
<?xml version="1.0" encoding="utf-8"?>

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

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

xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">

<fx:Declarations>

<!-- Place non-visual elements (e.g., services, value objects) here -->

</fx:Declarations>



<mx:Tree labelField="@tag" showRoot="false">

<mx:dataProvider>

<fx:XML>

<note tag="My File">

<note tag="Book"/>

<note tag="Video"/>

<note tag="Homework"/>

<note tag="Photos">

<note tag="family"/>

</note>

</note>

</fx:XML>

</mx:dataProvider>

</mx:Tree>

</s:Application>


Hello! This article is talking about how to write ActionScript in your flex application. There are two ways to write ActionScript in a Flex application. First option is putting ActionScript code within MXML file. This is quite common when handling events. But this approach is best for short pieces of ActionScript. You can place it within Script tags as below:

<fx:Script>
<! [CDATA[
// ActionScript goes here!
]]>
</fx:Script>

Note that Script is defined within the Flex Core components namespace, fx. This namespace isn’t used in the first two chapters, although Flash Builder adds fx:Declarations tags to the default MXML file.

Also, you should surround your code with the <![CDATA[ and ]]> tags Because the MXML file is XML, many characters commonly found within ActionScript will be invalid when the XML interpreter looks at the page. By wrapping the ActionScript within those tags, the ActionScript code will be ignored by the XML interpreter.

A second way to add ActionScript to a Flex application is to store it in a separate text file. There are two primary benefits to going this route and I really recommend this way. First, it makes it easier to navigate and develop your application, with content in multiple files, saving you from searching through increasingly large and complex MXML documents for any particular code.

The second benefit is that once you’ve separated some ActionScript into another file, you can easily reuse it in other projects. Although it’s considered to be a best practice to write your ActionScript in a separate file, most of the examples in many books you read will not do so, because for the sake of simplicity.A separate ActionScript file can then be included by, or imported into, the MXML document. From a functional standpoint, including an ActionScript file has the same effect as if the code were inserted directly into the MXML. So, up to you which way you want to choose to develop your flex projects. I hope you will enjoy coding and have more fun.

This video is from Adobe. It is good for beginner to have a overview of flex and flash builder. Learn about the basics of using Flex and Flash Builder, including setting up Flash Builder, building data-driven Flex applications, and organizing visual elements and code. In this episode of the Flex in a Week training series, you will learn which technologies make up the Adobe Flash Platform.

Enjoy coding and have more fun.

Hello, I found this nice toturial for creating Httpservice with adobe flash builder CS5. It is really easy to learn more. I tried it. It works very well. I hope you are doing well. Enjoy coding and fun.