On Sun, Jan 17, 2010 at 4:24 PM, Martin Aspeli wrote:
> Any chance we could put this in a separate view utility instead of the
> @@plone one, so that it's more sane to override?
Yeah. With bodyClass already being on that view, it felt ok-ish. But I
guess there's a couple of "visual policy" method
Hi,
2010/1/17 Hanno Schlichting :
> On Sun, Jan 17, 2010 at 4:24 PM, Martin Aspeli wrote:
>> Any chance we could put this in a separate view utility instead of the
>> @@plone one, so that it's more sane to override?
>
> Yeah. With bodyClass already being on that view, it felt ok-ish. But I
> gues
On 2010-1-17 16:52, Hanno Schlichting wrote:
On Sun, Jan 17, 2010 at 4:24 PM, Martin Aspeli wrote:
Any chance we could put this in a separate view utility instead of the
@@plone one, so that it's more sane to override?
Yeah. With bodyClass already being on that view, it felt ok-ish. But I
gue
On Sun, Jan 17, 2010 at 9:19 PM, Wichert Akkerman wrote:
> On 2010-1-17 16:52, Hanno Schlichting wrote:
>>
>> mark_view
>> have_portlets
>> hide_columns
>> renderBase
>> bodyClass
>
> is_view_template or whatever it is that manages IViewView. We've found it to
> be very painful to manage IViewView
On 2010-1-17 21:36, Hanno Schlichting wrote:
On Sun, Jan 17, 2010 at 9:19 PM, Wichert Akkerman wrote:
On 2010-1-17 16:52, Hanno Schlichting wrote:
mark_view
have_portlets
hide_columns
renderBase
bodyClass
is_view_template or whatever it is that manages IViewView. We've found it to
be very p
On Sun, Jan 17, 2010 at 9:38 PM, Wichert Akkerman wrote:
> class MyView(BrowserView):
> def __call__(self):
> return aq_inner(self.context).some_template()
>
> and make sure that IViewView is set when some_template is rendered.
> Currently that is impossible since mark_view does checks t
