Re: [Webmacro-devel] ContextTool replacement and thread-safety

[Brian G. <br...@qu...>]

> Why do we need any of this magical stuff in WebMacro?
> 
> > So - magic everywhere, or nowhere?
> 
> Come on Marc, who's side are you on here?  :)  Magic *nowhere*
> 

This seems like a conversation worth having.  I think that while you
and Marc agree on the idea of ditching (or at least demoting) CT, your
motivations are different.  

Lets talk about this magic thing.  I have always thought that the
magic "architect selects tools { X, Y, Z } and makes them available
transparently in all contexts" to be a powerful feature.  Velocity has
a similar mechanism for loading global macros (which we should have
too.)  

You seem to think its bad, and not in the user's best interest.
Explain.