[thelist] zope cms implementations?

[george]

hey, thanks for the kind words.

You can try browsing through the CMF site howtos's:
http://cmf.zope.org/doc

and this:
http://cmf.zope.org/Members/beehive/ZWACKChap5.html/view

but generally zope does have that documentation problem where things get
implemented and distributed and the docs are not much of a priority.

the basic page layout is defined in the portal_skins tool and the convention
is to create a standard_html_header and a standard_html_footer which will
contain the basic template and then include them at the top and bottom,
respectively, of all your pages with <dtml-var standard_html_header> or
footer as the case is.

and then the default view for example for a newsitem is i think
newsitem_view and you can customize this. same for the other content types.
the hard part is sometimes searching for all the methods that make up
things.

and this architecture is not documented AFAIK. I went thru the methods and
figured it out for myself. didnt take too long :-)

ZPT might be of interest to you. i havent taken the time to check it out
yet.
http://www.zope.org/Members/4am/ZPT

good luck with the zope experience!

un abrazo,
george
http://cyklotron.com/
cyklotron: a gringo in medellin, colombia

> From: Sam-I-Am <sam at sam-i-am.com>
> I guess I'm just having trouble understanding what the pieces do and how
> it all fits together. At what point is a basic page layout defined, and
> how do I make variations on this.. and how do I give a look/feel to
> individual sub-templates/ or areas of a given page, or views of a
> particular content object.. Maybe my question is the best clue to how
> clueless I am. Is the very high-level object architecture documented
> somewhere, somewhere that says these are the pieces, here's what they
> do, here's how you go about creating more or customizing the existing
> ones? 
> 
> [more browsing]
> 
> ah.. now the xhtml templates proposal makes more sense to me.
> http://www.zope.org//Wikis/DevSite/Proposals/XHTMLTemplatesProposal
> And this also tells me why I wasn't understanding the current
> architecture in the first place - it's awful! (from a separation of the
> presentation layer point of view)
> 
> thanks
> (I really liked http://zettai.net/ and http://cyklotron.com/ btw)