2010/1/17 Hanno Schlichting <ha...@hannosch.eu>:
> On Sun, Jan 17, 2010 at 4:24 PM, Martin Aspeli <optil...@gmail.com> 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" methods in there which
> should go into their own view somewhere in plone.app.layout.


> Just looking at the methods, I'd move the following to a new view
> (leaving BBB support in the old place):
> mark_view
> have_portlets
> hide_columns
> renderBase
> bodyClass
> These all feel like things that influence CSS classes or UI policy in some 
> way.

I think mark_view should probably stay, or at least be separate. It's
both fundamental to other functionality and easy to screw up. +1 for
the others, though.


Framework-Team mailing list

Reply via email to