On Sunday 16 April 2006 15:17, Jeff Rush wrote:
> Perhaps most of you already know this but it bit me this week.  For my
> project I've noticed some sluggish presentation of pages, and a lot of
> container queries flying around for very simple pages.  It turns out to be
> Javascript code (singleBranchTree.xml) that is walking one-level of
> parents, siblings and children for each of my pages, even though I don't
> have a nav tree widget in my skin.
> I thought I was doing things the preferred way, by using the existing
> @@standard_macros/page and filling in slots to change out selected
> portions. It turns out that while there is a slot to disable the -display-
> of the nav tree, there isn't one for the page header to disable the
> -computation- of the nav tree, which is triggered from within the browser
> via navigation_tree.js upon the body load event.

I would always write a skin from scratch. Roger Ineichen has developed a set 
of minimal registrations (like error pages, etc) for a new skin. He should 
probably release that code, if he has not already.

Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
Zope3-users mailing list

Reply via email to