I was having so much trouble getting substacks of substacks to work, and the main reason I was doing this was to gain access to the handlers, that I ended up re-arranging all the handlers and putting almost all of them in the mainstack stack script, leaving only specific openStack (and things like that) in the separate stack scripts.
This required only minor handler modifications to tell each handler *which* stack the request came from because "this stack" was no longer appropriate in most cases. This is "ok", but I was hoping to be able to do this more modularly - keeping all of a particular stack's handlers within a substack. But as soon as I needed a depth of more than 2 (a substack of a substack) this became unfeasible. So the entire project is a lot less modular than would be nice if we wanted to allow a group of people to work on the project. I think better support for a more flexible stack hierarchy would be useful in future Rev enhancements. Especially for groups of people working together on a single project, or for creating plugin features to an existing app. doug _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
