you looked at NSTreeNode?
I didn't - thanks for this hint :) And it looks perfect if I decide
to
implement my own container, but I'm going to search some more
opportunities.
Beyond NSTreeNode, what more do you have to implement? (i.e. there
needn't be any container for a tree data structure
instances of just one small object, the node itself. Usually that's
all you have to code and it's all self-referential.
--Graham
Please let's not forget that a tree data structure is often pretty
much useless without some form of balancing. Otherwise, in the worst
case, what you really have
On 06.05.2009, at 10:24, Andreas Grosam wrote:
Luckily, I don't need such a beast. ;) I just need a graph, a
hierarchical data container - no search tree.
An NSDictionary with an NSArray under the key @children should do
the trick.
Cheers,
-- Uli Kusterer
The Witnesses of TeachText
to implement? (i.e. there
needn't be any container for a tree data structure, it can be
composed completely of its nodes).
Well, this depends on your requirements and whether it is a search tree or
a graph.
In my actual case I wont need much functionality.
Some possible requirements may
NSTreeController and CFTree is not exactly what I'm searching for. I
would like to have a *pure*, simple and effective but complete tree
data structure which comprises a hierarchy of objects:
root
|- object1
|- object2
|- object4
|- object5
The container shall be sequential
On May 5, 2009, at 8:10 AM, Andreas Grosam wrote:
NSTreeController and CFTree is not exactly what I'm searching for. I
would like to have a *pure*, simple and effective but complete tree
data structure which comprises a hierarchy of objects:
[...]
Well, first of all, it's easy enough
Grosam agro...@onlinehome.dewrote:
NSTreeController and CFTree is not exactly what I'm searching for. I would
like to have a *pure*, simple and effective but complete tree data
structure which comprises a hierarchy of objects:
root
|- object1
|- object2
|- object4
|- object5
On May 5, 2009, at 3:21 PM, Ken Thomases wrote:
On May 5, 2009, at 8:10 AM, Andreas Grosam wrote:
NSTreeController and CFTree is not exactly what I'm searching for.
I would like to have a *pure*, simple and effective but complete
tree data structure which comprises a hierarchy
On 06/05/2009, at 1:28 AM, Andreas Grosam wrote:
Please don't underestimate the effort to just roll your own.
Nor overestimate it ;-)
Bear in mind that a simple tree can be implemented using multiple
instances of just one small object, the node itself. Usually that's
all you have to
, the node itself. Usually that's
all you have to code and it's all self-referential.
--Graham
Please let's not forget that a tree data structure is often pretty
much useless without some form of balancing. Otherwise, in the worst
case, what you really have is a degenerate form of your tree
On Tue, 2009/05/05, WT jrca...@gmail.com wrote:
From: WT jrca...@gmail.com
Subject: Re: A tree data structure?
To: Cocoa-Dev List cocoa-dev@lists.apple.com
Date: Tuesday, 2009 May 5, 12:19
Please let's not forget that a tree data structure
is often pretty much useless without some form
11 matches
Mail list logo
