Carsten Ziegeler wrote:
He he, I usually agree with your approach, but this time, it's too
complicated for me. My real-world use-case is that I'm thinking about
using cocoon blocks as a mechanism to write portlets for the cocoon
portal engine. You end up with having the portal engine block and
several portlet blocks. And here you exactly need the scenario I
described. Sorry, but I will not provide a prototype for this :)
So my question is: does this make sense?
Carsten
Sure, it makes sense that "cocoon portlets" could be blocks unto
themselves. In fact, that would be a great way to separate the portal
functionality from the portlets. The portal just needs a way to discover
they are there.
Ralph
