[z3-five] index_html in CMF-2.0.0, Zope-2.9.1 and Five

[David Pratt]

Yes, and I have a number of instances like this. At this point it looks 
like one would need a marker interface per folder instance or do more 
object subclassing to provide more specific object types that offer 
their own interface to solve this. Am I correct?

I wonder what other folks plan to do about this (like the plone folks) 
since I think they have customizable member pages and parts of their 
portal that use this approach. A portal folder can only provide one 
default view. I believe this is where things fall apart because there 
was more flexibility with less effort.

What's more is that I have used the same approach with the main_template 
to provide a visual boundary between the portal administrative area. 
Same sort of thing - it overrides the main_template and uses other css, 
etc. I have no idea how to solve this one right now since this is again 
more than one default in a site. Any ideas would be welcome to help me 
get my head around the conversion to Five views. This is real world Z2 
stuff that I am trying to sort through to get to the Z3 goal.

Regards,
David


Paul Winkler wrote:
> On Sun, Mar 05, 2006 at 09:01:16PM +0100, Lennart Regebro wrote:
> 
>>On 3/5/06, David Pratt <fairwinds at eastlink.ca> wrote:
>>
>>>Creating a folder with a public view outside a CMF instance still does
>>>the right thing and you can edit and view an index_html as you always
>>>could before.
>>
>>No it's actually quite unusual in CMF, I think. I sure never seen anybody do it.
> 
> 
> I've seen it a lot. It's often desirable to have a different
> default view for folders in different sections of the site.
> Usually the content managers would create it as a Document or similar
> content object named index_html.  It's quick, easy, and works without
> developer intervention.
>