Hi Amy, I replied to your mail because it was the last in the conversation (I do not use the web based interface-just gmail), and i usually reply to the last message and not the original question...Does this mess up the web view?
Your solution is similar to mine, i just use a custom data structure where you chose to use the framework provided one. As for the 'icky' bit, are you sure that your hierarchical data structure does not use pointers to parent nodes internally? (Have not used it so i do not know) Cheers, Fotis PS: I am not arguing with anybody :-) (even though sometimes I am tempted to reply to some extremely caustic lines of text...) On Thu, Dec 18, 2008 at 5:03 PM, Amy <[email protected]> wrote: > --- In [email protected] <flexcoders%40yahoogroups.com>, "Fotis > Chatzinikos" > <fotis.chatzini...@...> wrote: > > > > Depends on your style / preferences... XML might be easier to > handle but > > arrays are much faster to wire and compute.. > > > > I use the following array based structure , where parent helps > upward tree > > traversal (children contains CategoryTree instances): > > > > public class CategoryTree > > { > > public var label:String ; > > public var children:ArrayCollection ; > > public var parent:CategoryTree; > > } > > I think maybe you're arguing with Tracy in your reply to me :-). I > was suggesting that you use objects with a children property that's > an ArrayCollection. You then cast the top level ArrayCollection or > Object to HierarchicalData and cast that to > HierarchicalCollectionView and use getParentItem() to retrieve a > reference to the parent from the child. > > I, personally, think it's a little "icky" to store a reference to an > object higher in the hierarchy (that hence contains a reference to > this object that has a reference to the parent...), so I think I'd > probably feel a bit suicidal if forced to do so. :-) > > But hey, whatever works. > > -Amy > > > -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation [email protected],
