> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
>
> I would also suggest that your suggestion is out of sync with the
> relevant topics being raised.  Leo has raised a technical issue which
> nobody seems interested in addressing.  Berin has raised political issue
> which in my opinion is not in scope.  Should this thread die then maybe
> Leo's question will be addressed - in the meantime the rest is IMO just
> noise.  Honestly - if people cannot put together technical arguments
> then they need to reconsider their respective positions.

Stephen, 

The matter is completely in sync since the old documentation did NOT make a
claim that constructor injection was part of the traditional Avalon 4.2
framework.  Those documents and comments were only under the "Merlin"
section.  Leo's concern grew from the release of the new site, the
elimination of the framework docs, and the claim that the constructor
injection feature is part of the general Avalon framework.

I've given you a list of concerns which included Leo's:

1. Drop of Avalon Framework as a "product"
2. Lack of Framework 4.1 documentation or any "framework" documentation at 
   all (the only related docs are labeled under "component specification")
3. Concern and confusion about the constructor injection feature moving
   from a Merlin-specific enhancement to a general Avalon framework feature.
4. General concern and confusion about the role of the traditional framework
   library in Avalon's future.

And here are the proposed solutions:

1. Re-introduction of prior Avalon Framework documentation
2. If constructor injection is to be part of the general Avalon framework, 
   we should consider a major version jump to Avalon 5.0 out of respect for
   the various Avalon related projects.

Now, as I stated before, would you like to address these or are you only
interested in "political" rants of your own?

J. Aaron Farr
  SONY ELECTRONICS
  STP SYSTEMS
  (724) 696-7653

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to