J Aaron Farr wrote:
Hello.
Just a little reality check on Fortress capabilities:
-- All Fortress components exist on the "root" level. In other words, they
are defined on the same level in the *.xconf file.
Correct.
-- If you wanted to have "nested" components which were also handled
(initialized, etc.) by the root container, you would need to extend the
Fortress DefaultContainer in some way.
Right.
I'm also wondering about "subcontainers" -- kinda like Pheonix Blocks. Is
there anything comparable to this in Fortress or even Merlin? In other words,
you have a DefaultContainer and one of it's components is also another
DefaultContainer, or something like that. Does that make sense?
Yep. That definitely works. Another approach that I thought of was to
extend the DefaultContainer to directly embed child containers and hand
stuff off to the child container that is responsible for handling the
requests.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
