I agree with Eric. Your basic issue is the way you're forming your XML.
First, the way you have it, there is no need to have a hierarchy. This
would work just as well:
<people>
<person name="Ted" title="director of the world" />
<person name="Jim" title="Manager - North America" />
</people>
It would be better, though, to make the node names meaningful and
hierarchical. So, something like this:
<management>
<world>
<directors>
<director name="Ted" title="director of the world" />
<deputy name="Bob" title="deputy director of the world" />
</directors>
</world>
<continent>
<country>
<managers>
<manager name="Canada" manager= "Jim" title="Manager - Canada">
</managers>
<leads>
<lead name="Sampson" title="Lead - Western States"/>
<lead name="Sophia" title="Lead - Eastern States"/>
</lead>
</country>
</continent>
</management>
You could come up with a better structure than that, I'm sure, but
that's the basic idea.
Cordially,
Kerry Thompson
On Mon, Mar 22, 2010 at 1:59 PM, Eric E. Dolecki <[email protected]> wrote:
> How about having the nodes be more descriptive?
>
> <director name="Ted"
> <deputy name="Bob">
> ...
> </deputy>
> </director>
>
> Then use those node names
>
> On Mon, Mar 22, 2010 at 1:33 PM, Lehr, Theodore
> <[email protected]>wrote:
>
>> Perhaps I do have a bigger issue (actually, I have LOTS of issues ;-), but
>> the reason I need to know the depth is my thought was to use that as a means
>> of assisting in layout.... for example, say you have the follwing xml:
>>
>> <person name="Ted" title="director of the world">
>> <person name="Bob" title="deputy director of the world">
>> <person name="Jim" title="Manager - North America">
>> <person name="Sampson" title="Lead - Western States"/>
>> <person name="Sophia" title="Lead - Eastern States"/>
>> </person>
>> <person name="Sally" title="Manager - South America"/>
>> <person name="Sarah" title="Manager - Africa"/>
>> </person>
>> </person>
>>
>> And you used this to create an organizational flow chart... my thought was
>> to use the depth to figure out where the names should go... I have thought
>> about how to do this 12,002 ways so my head is getting muddled....
>>
>> ________________________________________
>> From: [email protected] [
>> [email protected]] On Behalf Of Steven Sacks [
>> [email protected]]
>> Sent: Monday, March 22, 2010 1:15 PM
>> To: Flash Coders List
>> Subject: Re: [Flashcoders] xml: counting parents
>>
>> I think you mean ancestors. A node can only have one parent. Parents can
>> have
>> many children.
>>
>> I think you have a bigger issue, though. Why do you need to know the depth
>> of an
>> xml node? I can't think of a single example that I would need that
>> information.
>>
>>
>> On 3/22/2010 9:27 AM, Lehr, Theodore wrote:
>> > I am still trying to find a way to see where a child is within the xml -
>> on what level... is it possible to count a nodes parents?
>> >
>> > So if I had:
>> >
>> > <person att="1">
>> > <person att="2">
>> > <person att="3"/>
>> > <person att="4"/>
>> > </person>
>> > </person>
>> >
>> > 1 would return that it has 0 parents, 2 would say it has 1 parent, 3& 4
>> would say they have 2 parents....
>> >
>> > hope that makes sense....
>> >
>> > Ted
>> > _______________________________________________
>> > Flashcoders mailing list
>> > [email protected]
>> > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>> >
>> _______________________________________________
>> Flashcoders mailing list
>> [email protected]
>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>> _______________________________________________
>> Flashcoders mailing list
>> [email protected]
>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>>
>
>
>
> --
> http://ericd.net
> Interactive design and development
> _______________________________________________
> Flashcoders mailing list
> [email protected]
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
