Paul Hammant wrote:
> Stephen,
>
>> There is now 2 -1s on BlockContext.
>
>
> I like BlockContext.
> +1
>
> ( By my reckoning you are now at only -1 )
Naa, he withdrew them.
Paul, it's not about what I like or what you like or what John Doe likes.
BlockContext is a dependency to Phoenix, and *if* we want to make
cross-container compatible components, it's not a solution.
It binds you to Phoenix, but I assume that it's not a problem for you,
you also made a GUI in Phoenix, so I understand you don't see the point.
But Avalon is not only Phoenix, and as Peter pointed out he would like
to be able to use Cocoon components.
I would like to use Phoenix components.
If I make the Cocoon components dependent on CocoonContext, it would not
make reuse by Phoenix possible.
Think about this, instead of just saying "I like it".
Let me be more clear if I can: Phoenix has a specific Context that it
only can use. It's needed, regardless to how itthere; it's needed, and
from a functionality POV I like it too.
But we also like to see components be able to work accross containers,
so the dependency has to be quite strong IMHO, or else it means that the
functionality it provides is general enough for quite all containers.
Now, given that most containers have some need from this stuff, Peter
rightly went on with containerkit, so that similar containers can share
the same underlying system.
And introduced attributes which are a terrific way to specify additional
stuff.
So the thing should be dealt with on two levels, which we are doing:
1) define common attributes and possibly common Context keys to access
common functionality
- thus we need to have a simp�le way of telling in the descriptor what
Context is needed.
2) provide a "standard" implementation for "standard" containers of
concrete implementations of the framework, which is Containerkit.
- Now it seems to me that BlockContext would be an excellent candidate
for the containerkit Context.
I would humbly propose to maybe put the BlockContext in containerkit,
deprecate the one in Phoenix, make the Phoenix one extend the
containerkit one for compatibility, and make Cornestone blocks, which
IIUC Peter also would like to see a components in excalibur (or
something like that), use the containerkit context.
What do you think, is it viable?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
