Stephen McConnell wrote:
I guess this also includes that the framework will not be developed separately anymore as a general basis for containers?
<snip/>
The choices are really open.
But not obvious, especially to a new user or someone not familiar with the nuances of Avalon.
I noticed the lack of framework docs last night and I feel a dedicated section belongs with the other "subsystems" at:
http://avalon.apache.org/products/runtime/system/index.html
The problems with the 'assimilated' approach are
- From a component author perspective the Avalon framework is the
point of contact between my personal development and all this
Avalon stuff. - There are many other projects and applications which only use the
Avalon framework. These groups will be interested in framework
documentation which discusses it in a more 'standalone' context.Whether there is another product icon on the front page for the Framework is another matter (which might not be a bad idea). IMHO the current docs are fine for describing the specification and how Merlin implements the framework, but don't cut it for discussing the framework itself.
Just my $0.02
jaaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
