Then I came across this blog when surfing around on the internet earlier this week…

Therefore, no indexed array.

it runs without adding any childern. My arrays are below.

This is my top level:
["admin"] => array(4) {
["parent"] => string(1) “0″
["id"] => string(5) “admin”
["branch_name"] => string(28) “mttdeveloper/refactor/action”
["label"] => string(5) “admin”
}
["mttauthacl"] => array(4) {
["parent"] => string(1) “0″
["id"] => string(10) “mttauthacl”
["branch_name"] => string(28) “mttdeveloper/refactor/action”
["label"] => string(10) “mttauthacl”
}
["mttdeveloper"] => array(4) {
["parent"] => string(1) “0″
["id"] => string(12) “mttdeveloper”
["branch_name"] => string(28) “mttdeveloper/refactor/action”
["label"] => string(12) “mttdeveloper”
}
}

Second Level looks like this:

["admin"] => array(4) {
["parent"] => string(5) “admin”
["id"] => string(5) “admin”
["branch_name"] => string(5) “admin”
["label"] => string(5) “admin”
}
}

branches look like this with out their children.

array(2) {
["admin"] => array(5) {
["id"] => string(5) “admin”
["label"] => string(5) “Admin”
["path"] => string(30) “/mttdeveloper/refactor/action/”
["iconClass"] => string(6) “folder”
["children"] => array(0) {
}
}
["demo"] => array(5) {
["id"] => string(4) “demo”
["label"] => string(4) “Demo”
["path"] => string(30) “/mttdeveloper/refactor/action/”
["iconClass"] => string(6) “folder”
["children"] => array(0) {
}
}
}

Martin de Keijzer :
Great review, it’s good to see people enjoyed theirselves. Comments like these make organising a big event like this throughout the year worthwhile!

I guess the main reason why they enjoyed themselves was that their host was very hospitable and considerate. Not many organizers are like that. I’ve encountered a few not-so gracious hosts myself.

Well said. When I started out with ZF I encountered the Actionstack, and a whole load of problems – many of which you touch on.

I couldn’t agree more. I got a boatload of probs when I first started using Zend and the Actionstack. You touched on many of those issues. Just clarifies my thoughts on things…..

Actionstack is not evil :
Hello,
Actively developing with zf you can’t avoid hearing this over and over again, people compalining about the actionstack. I understand that you CAN make partials and views that render and fetch different stuff from the models. However, to create trully modular components, actionstack is a logical way to go (if actionstack really is such a bottleneck for performance maybe it should be made lighter).
I have created an architecture which has dynamic modules that belong to some zone in a layout. The actionstack is used to make all the modules render themselves with their indexaction. For this reason I could just take that module and only use it solo because in indexaction it only echoes it’s own content. If you are using view scripts to also display actions of several modules in your page it is not really modular. I don’t know if you understand what I’m saying and I do get that actionstack gives overhead but it is still the thing that makes my modules the most logical I can have them.
One thing though, I have never found the need for the action view helper and can’t really see a real use case for that one
Cheers

Hello My Friend,
Can you tell me how did you do that?
How to echoes layouts->widgetized with the calling name of a nameAction?