hey michel, in regards to the tree navigation my setup is really simple. the documents in the tree are simply <standard_html_header> <document content goes here> <standard_html_footer> where the <tree> tag block itself is in the <standard_html_header>. so both document content and tree are in one DTML document, just a simple table setup. it's the very same layout used in the ZBook tutorial on creating a simple setup with a tree. in my case, since there is just one "chapter" (one book icon) it would be sufficient if i could just make that book appear open and revealing the few pages in it. Jens

-----Original Message----- From: michel@localhost.localdomain Subject: Re: [Zope] Tree navigation

Jens Vagelpohl wrote:

...

hi everyone,

this morning a list member had a question about how to synchronize a tree with a page being opened, i am trying to do the very same. it is not a problem to create a link to the specific document within the tree, but how can i make sure the tree that displays the navigational choices (it's in the standard_html_header of the document i am displaying) is in synch with the page i am linking to, meaning the book is "open"?

DO you mean you want a tree in one HTML frame, that is acurately mapped to the state of a document in another HTML frame? Or do you want both the tree and the document in one and the same frame? The second is probably fairly straightforward, the first would require some javascript tricks.

...

something else. in regards to michel's Question, i think it might be really hard to adequately describe zope in one sentence.......................... :)

That's why I asked. ;)

-Michel

...

Jens Vagelpohl

On Fri, 23 Jul 1999, Michel Pelletier wrote:

DO you mean you want a tree in one HTML frame, that is acurately mapped to the state of a document in another HTML frame? Or do you want both the tree and the document in one and the same frame? The second is probably fairly straightforward, the first would require some javascript tricks. The second isn't as easy as one would think. The tree tag [+]/[-] links do not include the query string, which produces error if the currently display document happens to need the parameters, like some SQL results.

I'd probably prefer the tree tag include the QUERY_STRING of the current REQUEST when generating the fold in/out URLs, this would make creating websites much easier. A completely another thing are POSTed pages, they should probably not be reincluded automatically in the URL. Why? The HTTP RFC specifies, that POST should not be repeated without user interaction, because it might alter the state of the Webserver (like creating some object), while GET methods may be repeated without side effects. That's also why netscape asks `Repost form data' when reloading a page that resulted from a POST. Andreas -- Win95: n., A huge annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS, Win 3.x, Win98.