Etria Lists

Justin Ryan wrote:

> I see that yours is very simple and lightweight, driven by interfaces,
> which I like. I am concerned that it may make more sense for some
> portlets to be attached to the instance, so that they use existing
> machinery to allow contained objects to inherit as Plone3 users are
> learning to expect.

That should still work.  The current setup for (non-persistent) weblog 
sub-objects like ITopics is that they simply get the same portlets that 
their parent weblog gets - that includes context-specific portlets that 
have been setup by hand.

>  However, I can see some advantage of your request
> marking idea, and I wonder if the 'interfaces' category behaviour
> could possibly care about parent interface, or if that would even be a
> good idea at all.

The trick with the interfaces category portlet is to make it possible to 
*additionally* have weblog-ish portlets, but not have to register them 
for every extra portal_type that QuillsEnabled supports.



Tim