Re: Dynamically Processing Nodes

Hi Diez,
 
Attached is a test class which sort of simulates what should happen.
Take a look at the "showRecursively()" function.
This accomplishes what is needed making use of recursion.
How do I translate this into our iterative model?
 
SJ

>>> [email protected] 12/8/2003 4:58:22 PM >>>

Hi,

> Lets see if I have it correctly.
> You are saying that we should take the existing 'tree' structure,
> create a list from it and then render the rows from this list.
>
> If my interpretation is correct, then the rows would know in which
> order they must be rendered but not how the hierarchy should look.
> Therefore, I dont think this approach would work.

> I think that the hierarchy problem can be solved by some type of
> recursive functionality.
> Is there not, perhaps, a recursive model (wishfull thinking) ?

The recursion takes place when flattening the tree - in Kirks example,
you 
then had to annotate the list items with context information like depth
from 
this recursive decent.

The reason for that was that Kirk had a linear table structure - no 
hierarchies there, only colspan/rowspans to indicate indentation and
the 
like. So - you _have_ to break down things to a list.

Now if you have actually hierarchies of objects to render and that
strucure is 
reflected in the markup - then you go with parent-child models. Werner
Koch 
just gave you an example how that works. Basically, for every level of
your 
tree you have one model. His example has two levels, but you can have
an 
arbitrary number of them. These models communicate, so the inner model
gets 
notified of a new list of objects to render if the parent model
approaches a 
new object with childs in it.

Usually thats sufficient - its difficult to render content that has
random 
depths. But of course one might think of such an example - e.g. a
site-map. 
If you need to render such a thing, you should go for a custom
component that 
will insert markup recursively. You for example do that kind of stuff
using 
BLists. AFAIK this has been done before.

Please keep in mind that BTemplate is about heavily layouted stuff -
your 
designer gives you HTML that is suitable for lets say three levels.
Just 
stuffing recursively the same template into itself won't result in
predicable 
output - which is what we are after, at all :)

Did that help?

Diez

_______________________________________________
Barracuda mailing list
[email protected]
http://barracudamvc.org/lists/listinfo/barracuda


---------------------------------------------------------------
“All views or opinions expressed in this electronic message 
and its attachments are the view of the sender and do not 
necessarily reflect the views and opinions of the 
Provincial Government Western Cape (“the PGWC”).  
No employee of the WCPG is entitled to conclude a 
binding contract on behalf of the PGWC unless he/she 
is an Accounting Officer of the PGWC, or his or her 
authorised representative.

The information contained in this message and its attachments 
may be confidential or privileged and is for the use of the 
named recipient only, except where the sender specifically 
states otherwise.  If you are not the intended recipient you 
may not copy or deliver this message to anyone.”