On Saturday 06 March 2004 00:42, Alex Karasulu wrote: > Don't forget the social engineering tasks in front of us are much harder to > deal with than the code which in my opinion is trivial. With this > perspective on the situation I hope you agree if not I ask that you at a > minimum entertain the idea since it's really not much of a big deal. Or is > it?
Or put in another way; As Stefano (I think?) says; "Great Code doesn't build strong communities. Bad code and unifying vision does." Just about everyone agrees Merlin is "bad code", so now let's get on with fixing it together, instead of picking on Stephen's effort. He is open to change, improvements and ways to do it better. But it doesn't work by saying "Merlin sucks, let's scrap it and start over (again)." Since I got involved in the internals, I think I have been the catalyst to; 1. Dramatically simpler Activation implementation. 2. CompositionEvent allowing the model to be changed in runtime. 3. Component level security. and in my 'playground', I am also playing with 1. Pluggable LifeCycle support, incl. AF4 as well as PicoContainer styles. 2. A more complete Event model for composition. And most of the actual work is carried out by Stephen. Once shown the "light" and convinced about the benefits, he is quick to pull in the same direction. BUT, I agree it is a lot of things to understand, especially about the start sequence, and that is an area where 'new ideas' also can form and grow. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
