[picocontainer-dev] Synopsis of my thoughts on Pico 2
"Michael Rimov" <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Organization | Centerline Computers, Inc |
| Message-ID | <018501c84c01$83ae0fc0$8b0a2f40$@com> |
Since so many of your guy's work seems to go unappreciated, I wanted to let you
know my thoughts of Pico 2...
1 - PicoBuilder is great. Easy to use, covers most of the normal cases. Very
very cool.
2 - Pico slightly shortened names covers my own gripes about the amount of
typing I always needed to do. Wonderful!
3 - The differentiation between Behaviors, Injectors, etc is great. Easy to
follow, good delineation. I also like the "wrap" capabilities on the
ComponentAdapterFactories. Perfect for assembling more complex chains of
factories!
4 - The changes to component Monitor are GREEEEEEEEEAAAAAAAT!
a - The ability to handle when a component is not found and return a new
value is spectacular. It allows us to rework the NanoWAR hierarchy so that
containers behave in a parent/child relationship without necessarily having
references to each other. Very very very cool. (And I would NEVER ever ever
have thought of working it that way!)
b - Also, the ability to monitor no component found events takes care of
the whole "*TracingPicoContainers". I'm perfectly ok with having those two
classes in gems dropped.
5 - Thank you for the cleanup of the NanoContainer API!!!!!!!!!!!! The
hierarchy is much more manageable now.
Anyway, Paul, Mauro, Konstantin, Jörg, and anybody else I might have
forgotten.... what you've done is absolutely wonderful and I wanted to take a
moment to let you know it.
-Mike
P.S. Happy New year, and sorry I missed it but a belated Merry Christmas too!
:D
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email