> > 3. I have no idea what the Decompose Branch and the Create Branch
> > components do. It seams all they do is take in or spit out an integer
> > or an integer with a Path{n} around it. Again, if I'm missing
> > something on how they need to be used then let me know.
>
> Branch paths are just lists of integers. These two components allow
> you to convert paths into integer lists and vice versa.
> Paths can also instantiate themselves from Strings. So you can plug
> "1;0;2;4" into a path parameter and it will parse that.
Okay, I'm starting to see more of a use for this now...
> > 5. I think one unified way of getting any data out of trees would be a
> > nice addition to the ones that are already there. This means that the
> > extraction of the data would have to be interpreted from the syntax of
> > what data you want, but I think that the syntax could accommodate
> > that. I'm not 100% sure about this one, and maybe its the programmer
> > in me speaking out, but it seams like I could get what I want much
> > faster by typing some numbers in a special syntax rather than
> > assembling a bunch of additional components just to get a very
> > particular piece of data out of a path.
>
> Probably. Looks like I'll have to come up with something like Regular
> Expressions for paths.
Sound very interesting....I don't think in needs to add to much syntax
to what's there for paths, but we'll see. The only thing that pops in
my mind at this moment is a means of accessing the data via index at
the end of a node....ex. {0;2;2} (0)...Maybe some ways to retrieve
multiple branches or multiple indexes...and a few key words like
"Last" or something.
-Damien
