Lennart Regebro wrote: > On 7/13/07, Tres Seaver <[EMAIL PROTECTED]> wrote: >> You can't ask "upstream" to produce a thousand different pipelineables; >> the interface there needs to be dirt simple, and *always the same.*. >> In particular, you can't return unicode *or* a pipelineable: that puts >> the policy choice in the wrong place. > > Right. Also, after further discussion of the issues, which I'll try to > put down in a sprint-report, we have concluded that the correct place > to do the theming-pipeline is most likely in the BrowserPublication, > because there you have access to the context as well as the published > object typically (being a view class). > Doesn't the published object, being a view class, have context and request as instance variables?
object.context and object.request should work to access these things. Or am I missing something? -Jim Washington _______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com