Question

Flex Tree from Complex XML

Asked by: enjay99

Hi Genius'

I have been struggling with this for about a week now so it is time to ask for some help.
I have a well formed XML file that I receive from a server (please see original.xml) and I would like to represent it as a tree that the user can click on a leaf and be able to edit the elements associated with that item in fields to the right of the tree (either a dataGrid or a series of textInput fields.)

My problem is how to get it into a tree and tightly bound to the XML.

All of the examples that I have found mysteriously change from xml with elements in it into XML with only attributes (something like tree_1.xml). This is not useful as the actual data I am using has many elements attached to each leaf and sometimes multiple attributes.

My gut feeling (with very little experience in these matters) is to reformat the original.xml into a tree structure (like tree_2.xml), bind it to an XMLListCollection and create a tree by using a labelFunction.

I have two problems with this approach:

1. XMLListCollection does not seem to like the tree structure XML
2. If I write a labelFunction like:

private function getTreeLabel(item:Object):String
{
var node:XML = XML(item);
if( node.localName() == "Desc" )
return node;
else
return null;
}

I can do this by using the HTTPService as the dataProvider I get the branches and leaves I want but I also get a blank tree item for each of the nulls

I hope I have described the problem clearly as it is now very late here.
Going around in circles and very tired, so any help would be much appreciated.

Best Regards,

original.xml
 
<treeID>103</treeID>
<treeType>Oak</treeType>
<branches>
    <branch>
        <id label="branch ID" dbid="0">290</id>
        <branchCode label="branch Code" dbid="1">A</branchCode>
        <branchTitle label="Title" dbid="2">Small Branch</branchTitle>
    </branch>
    <branch>
        <id label="branch ID" dbid="0">391</id>
        <branchCode label="branch Code" dbid="1">B</branchCode>
        <branchTitle label="Title" dbid="2">Big Branch</branchTitle>
    </branch>
</branches>
 
<leaves>
    <leaf>
        <id label="leaf ID" dbid="0">48</id>
        <leafCode label="leaf Code" dbid="1">xBBLeaf1</leafCode>
        <leafDesc label="leaf Description" dbid="3">Big Branch Leaf One</leafDesc>
        <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
        <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
        <leafSize label="Leaf Size" dbid="10">123</leafSize>
    </leaf>
    <leaf>
        <id label="leaf ID" dbid="0">138</id>
        <leafCode label="leaf Code" dbid="1">yBBLeaf2</leafCode>
        <leafDesc label="leaf Description" dbid="3">Big Branch Leaf Two</leafDesc>
        <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
        <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
        <leafSize label="Leaf Size" dbid="10">124</leafSize>
    </leaf>
    <leaf>
        <id label="leaf ID" dbid="0">49</id>
        <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
        <leafDesc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
        <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
        <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
        <leafSize label="Leaf Size" dbid="10">125</leafSize>
    </leaf>
    <leaf>
        <id label="leaf ID" dbid="0">44</id>
        <leafCode label="leaf Code" dbid="1">SBLeaf1</leafCode>
        <leafDesc label="leaf Description" dbid="3">Small Branch Leaf One</leafDesc>
        <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
        <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
        <leafSize label="Leaf Size" dbid="10">126</leafSize>
    </leaf>
    <leaf>
        <id label="leaf ID" dbid="0">42</id>
        <leafCode label="leaf Code" dbid="1">SBLeaf2</leafCode>
        <leafDesc label="leaf Description" dbid="3">Small Branch Leaf Two</leafDesc>
        <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
        <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
        <leafSize label="Leaf Size" dbid="10">127</leafSize>
    </leaf>
</leaves>
 
=================================================================
 
tree_1.xml
 
<tree>
<branches>
    <branch id="290" branchCode="A" label="Small Branch" />
        <leaves>
            <branch id="44" leafCode="xSBLeaf1" label="Small Branch Leaf One" />
            <branch id="42" leafCode="xSBLeaf1" label="Small Branch Leaf Two" />
            <branch id="49" leafCode="Uni" label="The Multi Leaf" />
        </leaves>
    </branch>
    <branch id="391" branchCode="B" label="Big Branch" />
        <leaves>
            <branch id="48" leafCode="xBBLeaf1" label="Big Branch Leaf One" />
            <branch id="138" leafCode="xBBLeaf1" label="Big Branch Leaf Two" />
            <branch id="49" leafCode="Uni" label="The Multi Leaf" />
        </leaves>
    </branch>
</branches>
</tree>
 
====================================================================
 
 
<tree>
<branches>
    <branch id label="branch ID" dbid="0">290</id>
        <branchCode label="branch Code" dbid="1">A</branchCode>
        <Desc label="Title" dbid="2">Small Branch</branchTitle>
        <leaves>
            <leaf>
                <id label="leaf ID" dbid="0">49</id>
                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
                <Desc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">125</leafSize>
            </leaf>
            <leaf>
                <id label="leaf ID" dbid="0">44</id>
                <leafCode label="leaf Code" dbid="1">SBLeaf1</leafCode>
                <Desc label="leaf Description" dbid="3">Small Branch Leaf One</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">126</leafSize>
            </leaf>
            <leaf>
                <id label="leaf ID" dbid="0">42</id>
                <leafCode label="leaf Code" dbid="1">SBLeaf2</leafCode>
                <Desc label="leaf Description" dbid="3">Small Branch Leaf Two</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">127</leafSize>
            </leaf>
        </leaves>
    </branch>
    <branch>
        <id label="branch ID" dbid="0">391</id>
        <branchCode label="branch Code" dbid="1">B</branchCode>
        <Desc label="Title" dbid="2">Big Branch</branchTitle>
        <leaves>
            <leaf>
                <id label="leaf ID" dbid="0">48</id>
                <leafCode label="leaf Code" dbid="1">xBBLeaf1</leafCode>
                <Desc label="leaf Description" dbid="3">Big Branch Leaf One</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">123</leafSize>
            </leaf>
            <leaf>
                <id label="leaf ID" dbid="0">138</id>
                <leafCode label="leaf Code" dbid="1">yBBLeaf2</leafCode>
                <Desc label="leaf Description" dbid="3">Big Branch Leaf Two</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">124</leafSize>
            </leaf>
            <leaf>
                <id label="leaf ID" dbid="0">49</id>
                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
                <Desc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
                <leafSize label="Leaf Size" dbid="10">125</leafSize>
            </leaf>
        </leaves>        
    </branch>
</branches>
</tree>

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:

Select all Open in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Plus...

30 Day FREE access, no risk, no obligation
Collaborate with the world's top tech experts
Unlimited access to our exclusive solution database
Never be left without tech help again

Subscribe Now

Asked On: 2009-05-13 at 04:35:50ID24404270
Tags: Flex 3 Tree XML
Topic: Adobe Flex
Participating Experts: 1
Points: 500
Comments: 6

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

"The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
"Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
"Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Free Tech Articles

WARNING: 5 Reasons why you should NEVER fix a computer for free.
It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
SCCM OSD Basic troubleshooting
SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
Create a Win7 Gadget
This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
Outlook continually prompting for username and password
There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
Backup Exchange 2010 Information Store using Windows Backup
There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

Avoiding Bugs in Microsoft Access
Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
Top 10 Best New Features in Visio 2010
Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
IT Consultant Business Secrets Revealed
Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
Disaster Recovery and Business Continuity
Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
Organize Your Visio Diagrams with Containers and Lists
Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
How to Us Objects, Properties, Events and Methods in Microsoft Access
Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Watch More

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

by: mplordPosted on 2009-05-13 at 05:42:56ID: 24374086

You are right, the tree XML you provide to the Tree control will need to be formatted in a way that the Tree control will accept. So you'll have to transform the XML you get from the HTTPService request before you can use it exactly as you need in the tree, then once edited transform it back to the format you require before sending it back for update etc.

Your tree_2.xml had to be modified slightly as your tags were not matching correctly (probably your tiredness right ;) - the following example should help you see how to show the complete (bound) tree including element values.

Remember though that elements are still children of the enclosing tags, so will always appear as child nodes in the tree. If for example you want to show the id element value as the label for the id node, you'll have to reformat your XML to provide the id value as an attribute of the id node then update the getTreeLabel function to build the label string.

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="init();">
 
	<mx:Script>
		<![CDATA[
			[Bindable] private var model:XML = 
				<tree>
					<branches>
					    <branch>
					    	<id label="branch ID" dbid="0">290</id>
					        <branchCode label="branch Code" dbid="1">A</branchCode>
					        <branchTitle label="Title" dbid="2">Small Branch</branchTitle>
					        <leaves>
					            <leaf>
					                <id label="leaf ID" dbid="0">49</id>
					                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
					                <leafDesc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">125</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">44</id>
					                <leafCode label="leaf Code" dbid="1">SBLeaf1</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Small Branch Leaf One</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">126</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">42</id>
					                <leafCode label="leaf Code" dbid="1">SBLeaf2</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Small Branch Leaf Two</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">127</leafSize>
					            </leaf>
					        </leaves>
					    </branch>
					    <branch>
					        <id label="branch ID" dbid="0">391</id>
					        <branchCode label="branch Code" dbid="1">B</branchCode>
					        <branchTitle label="Title" dbid="2">Big Branch</branchTitle>
					        <leaves>
					            <leaf>
					                <id label="leaf ID" dbid="0">48</id>
					                <leafCode label="leaf Code" dbid="1">xBBLeaf1</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Big Branch Leaf One</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">123</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">138</id>
					                <leafCode label="leaf Code" dbid="1">yBBLeaf2</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Big Branch Leaf Two</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">124</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">49</id>
					                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
					                <leafDesc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">125</leafSize>
					            </leaf>
					        </leaves>        
					    </branch>
					</branches>
				</tree>
				
				private function init():void
				{
					tree.dataProvider = model;
				}	
				
				private function getTreeLabel(item:Object):String
				{
					var node:XML = XML(item);
					if( node.localName() == null )
						return node.toString();
					else
					{
						switch (node.localName())
						{
							//eg
							case "leafDesc":
								return "leafDesc: " + node.@label;
								break;
						}						
					}
					// default
					return node.localName();
				}
		]]>
	</mx:Script>
 
	<mx:Tree id="tree" horizontalCenter="0" verticalCenter="7" width="472" height="380" labelFunction="getTreeLabel"></mx:Tree>
	
</mx:Application>

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:

Select all Open in new window

by: enjay99Posted on 2009-05-14 at 01:10:25ID: 24382573

Dear mplord,

Thank you for your excellent response, what a great service.

As you mentioned though all the elements are still children of the enclosing tags, so will always appear as child nodes in the tree.

I was hoping to use the getTreeLabel function to only list the Title of the branch or leaf, but bind to the rest of the data elements of the leaf for editing in another part of the screen.

Perhaps that is asking a bit too much of the flex tree and will have to create a tree of only the Titles and somehow "point" to the data for editing.

by: mplordPosted on 2009-05-14 at 04:55:23ID: 24383827

You can use a custom data descriptor for the tree to help with this.

I've created a new class CustomDescriptor which overrides DefaultDataDescriptor, and is provided to the tree as it's dataDescriptor.

You'll have to add an event to detect when you've selected a node in the tree, and bind your editing fields to the node depending on it's type etc.

Hope this helps.

###### MAIN APPLICATION
 
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="init();" xmlns:my="*">
 
	<mx:Script>
		<![CDATA[
			[Bindable] private var model:XML = 
				<tree>
					<branches>
					    <branch>
					    	<id label="branch ID" dbid="0">290</id>
					        <branchCode label="branch Code" dbid="1">A</branchCode>
					        <branchTitle label="Title" dbid="2">Small Branch</branchTitle>
					        <leaves>
					            <leaf>
					                <id label="leaf ID" dbid="0">49</id>
					                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
					                <leafDesc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">125</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">44</id>
					                <leafCode label="leaf Code" dbid="1">SBLeaf1</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Small Branch Leaf One</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">126</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">42</id>
					                <leafCode label="leaf Code" dbid="1">SBLeaf2</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Small Branch Leaf Two</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">A</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">127</leafSize>
					            </leaf>
					        </leaves>
					    </branch>
					    <branch>
					        <id label="branch ID" dbid="0">391</id>
					        <branchCode label="branch Code" dbid="1">B</branchCode>
					        <branchTitle label="Title" dbid="2">Big Branch</branchTitle>
					        <leaves>
					            <leaf>
					                <id label="leaf ID" dbid="0">48</id>
					                <leafCode label="leaf Code" dbid="1">xBBLeaf1</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Big Branch Leaf One</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">123</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">138</id>
					                <leafCode label="leaf Code" dbid="1">yBBLeaf2</leafCode>
					                <leafDesc label="leaf Description" dbid="3">Big Branch Leaf Two</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">B</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">124</leafSize>
					            </leaf>
					            <leaf>
					                <id label="leaf ID" dbid="0">49</id>
					                <leafCode label="leaf Code" dbid="1">Unileaf</leafCode>
					                <leafDesc label="leaf Description" dbid="3">The Multi Leaf</leafDesc>
					                <onbranchs label="Appear on branchs" dbid="5">AB</onbranchs>
					                <leafDate label="Leaf Date" dbid="7">12-04-09</leafDate>
					                <leafSize label="Leaf Size" dbid="10">125</leafSize>
					            </leaf>
					        </leaves>        
					    </branch>
					</branches>
				</tree>
				
				private function init():void
				{
					tree.dataProvider = model;
				}	
				
				private function getTreeLabel(item:Object):String
				{
					var node:XML = XML(item);
					if( node.localName() == null )
						return node.toString();
					else
					{
						switch (node.localName())
						{
							//eg
							case "leaf":
								return "leaf: " + node.leafDesc.children()[0].toString();
								break;
							case "branch":
								return "branch: " + node.branchTitle.children()[0].toString();
								break;
						}						
					}
					// default
					return node.localName();
				}
		]]>
	</mx:Script>
 
	<mx:Tree dataDescriptor="{new CustomDescriptor()}" id="tree" horizontalCenter="0" verticalCenter="7" width="472" height="380" labelFunction="getTreeLabel"></mx:Tree>
	
</mx:Application>
 
 
###### CustomDescriptor.as
 
package
{
	import mx.collections.ICollectionView;
	import mx.collections.XMLListCollection;
	import mx.controls.treeClasses.DefaultDataDescriptor;
	
	public class CustomDescriptor extends DefaultDataDescriptor
	{
		public function CustomDescriptor()
		{
		}
 
		override public function hasChildren(node:Object, model:Object = null):Boolean
		{
			if (node is XML)
			{
				var xmlnode:XML = node as XML;
				switch (xmlnode.localName())
				{
					case "leaf":
						return false;
					case "branch":
						return ((xmlnode.leaves as XMLList).length() > 0);
				}
			}
			return super.hasChildren(node, model);
		}
 
		override public function isBranch(node:Object, model:Object = null):Boolean
		{
			if (node is XML)
			{
				var xmlnode:XML = node as XML;
				if (xmlnode.localName() == "leaf") return false;
			}
			return super.hasChildren(node, model);
		}
 
		override public function getChildren(node:Object, model:Object = null):ICollectionView
		{
			if (node is XML)
			{
				var xmlnode:XML = node as XML;
				switch (xmlnode.localName())
				{
					case "branch":
						return new XMLListCollection(xmlnode.leaves.leaf as XMLList);
				}
			}
			return super.getChildren(node, model);
		}
 
	}
}

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:

Select all Open in new window

by: enjay99Posted on 2009-05-14 at 22:55:02ID: 24392597

Fantastic !!!

Thank you mplord.

by: enjay99Posted on 2009-05-14 at 23:00:55ID: 24392617

Sorry mplord,

Could you please ping one more note, so that I can award points.
I said thank you in a comment without realizing how things work.

by: mplordPosted on 2009-05-15 at 02:48:42ID: 24393668

Hi - no problem :)

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

For individual users
Instant access to solutions
Ask your tech questions
Start your 30-day Free Trial

Business Accounts

Perfect for organizations
Multiple users
Save over 36%
Create a Business Account

Answer for Membership

Earn free access
Showcase your knowledge
No credit card required
Sign Up to Answer

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...

Question

Flex Tree from Complex XML

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Flex 3 Tree XML

Adobe Flex

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press