[quills-dev] tim2p-towards-1.7 branch progress
Justin Ryan justizin at gmail.comTue Feb 19 17:42:59 UTC 2008
- Previous message: [quills-dev] tim2p-towards-1.7 branch progress
- Next message: [quills-dev] tim2p-towards-1.7 branch progress
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 19, 2008 8:41 AM, Tim Hicks <tim at sitefusion.co.uk> wrote: > > The approach taken in QuillsEnabled is to use ZCML to mark classes with > IPossibleWeblog and IPossibleWeblogEntry interfaces to indicate that > they are weblog-enable-able (to abuse language horribly). There is then > also an IWeblogEnhanced interface that is used to mark individual > objects/instances (Folders, currently) to indicate that they should be > treated as weblogs. > > This works fine for rendering portlets for the folder/weblog as we can > arrange for quills' portlets to show up only when the weblog has been > marked with IWeblogEnhanced. > > However, the Documents contained within the weblog/folder are only > marked with IPossibleWeblog, but I have not figured out a good/efficient > way of distinguishing between those IPossibleWeblog-marked instances > that are (in some sense) currently contained in an IWeblogEnhanced > folder, and those that are not. > I am curious: is the listing of entries limited to those with IPossibleWeblog marker? > We could register our portlets for all IPossibleWeblogEntry objects and > then have the renderer crawl up the aq_chain looking for an object > implementing either IWeblog directly (as in the Quills case) or > IWeblogEnhanced (as in the QuillsEnabled case). Somehow that feels a > bit heavy handed, although it may not actually come with performance > penalties as presumably zope's standard traversal mechanism will have > 'woken up' all parent objects. > Here's the ten dollar question: why don't the child objects inherit this portlet, as seems to be the default? > Another alternative is to mark the request object with an interface > during our custom traversal mechanism so that we know when we are > operating "inside" a weblog. > If I had a kitten in my lap, it would be scared. :-P An idea I had is that instead of rendering the portlet for content objects with a given interface, we might simply attach the quills portlets to a container when weblog-ifying it. This might nullify the ten dollar question above, but I am also concerned that it is a bit heavy handed. Cheers, J -- Justin Alan Ryan Independent Interaction Architect http://www.bitmonk.net/ * : +1-415-226-1199
- Previous message: [quills-dev] tim2p-towards-1.7 branch progress
- Next message: [quills-dev] tim2p-towards-1.7 branch progress
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the quills-dev mailing list