> The only thing that could change is the placement of Excalibur stuff in
> Commons, avalon-components or scratchpad.
I'm sorry, Nicola. I know I raised this question yesterday, and I'm still
not understanding this particular change.
Looking at a "layered" view of Avalon:
Model Current Sub-Project Proposed Sub-Project
+---------------------------+ ------------------- --------------------
| Avalon Applications | Applications Components
+------------------------+--+
| Avalon Components | | Components Components
+=====================+--| |
| Avalon Container | | | Phoenix, et al Container
+---------------------+ | |
| Avalon ContainerKit | | | Excalibur Container
+=====================+-----|
| Avalon Frameworks | Frameworks Frameworks
+---------------------------+
This terrible ASCII graphic is intended to show that everything sees
interfaces published by Avalon Frameworks, but (ideally) Components see only
Frameworks (and other Components) as exposed through the Container, and
Applications are (sets of) Components & configuration.
I could see Avanon-specific Excalibur code rolled into the Container
sub-project that Stefano proposes, which is what I've illustrated above.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
