Stepanossov, Kirill wrote:
Why does everybody here think that COP and inheritance don't mix? Who said that?Committers, if this accepted, could you still leave different "toolkits" for building customized containers available ?
Example: Cocoon will need the embeddable container to implement cocoon blocks, but cocoon blocks will have features that are cocoon-specific, so Cocoon will have to "extend" this container to fit its needs.
I know we'll have to do that.
Gosh, of course! this is why this is a 'framework'. we are not locking people in, we are just deciding what functionalities to implement in each profile but there we are not planning to make all method calls *final* for &deity;'s sake!The point is that no matter how many different containers Avalon would offer, there be always a project for which no suitable container would be found.
The history of this project showed pretty evidently how COP-patterns applied to community building creates fragmentation and isolation and friction. Toolkits might be technically easier to use to achieve user goals but are bad for the evolution of a coherent and focused development community.Either they may offer too much or too little. Personally, would prefer to have several "toolkits" for building the majority of possible containers + a few containers as examples of constructing containers from those "toolkits"...
Which one do you prefer: a technical solution that works now but might leave you alone in the future because the maintainer decided to do something else, of a technical solution that imposes some work on you but will be maintained for that point on by an active community?
It's your ass you're betting on Avalon, do you have the energy to maintain a one-man-show toolkit if the original showman leaves or is kicked out?
Wouldn't you be more confortable on a solution maintained by several different individuals? wouldn't it be harder to see the development effort disappear?
It's yous ass, dude, think about it.
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
