The Cocoon Sample "List of Docs" is now working properly, building the hyperlinks for each document. Reach it via the "docs" section of the Welcome page, or via the side-panel of a top-level document page.
I found a solution to the relative URI issue described below. In documentation/sitemap.xmap i simply defined another match to append a new <path> element to each <book> entry, to provide the pathname of each book to the final stylesheet. The map:aggregate then adds each map:part via a cocoon:/ URI. This led me to wonder about efficiency issues. Surely there is more than one way to solve such a problem. Does sitemap efficiency matter? If so, then we need to start a user tips document. --David On 22 Nov 2001 David Crossley wrote: > I just added a new sample and new documentation functionality > (to HEAD only) that generates a "List of docs". This aggregates > all **/book.xml and renders and normal doc page. This works > nicely and gives a one-page listing of all Cocoon documentation. > See Welcome page or from the Main side-panel. > > However, it needs to link to each document and i cannot > find a way to generate the link. After all of the book.xml files > have been aggregated, we only have relative URIs available. > > For example, when the stylesheet is dealing with > xdocs/userdocs/concepts/book.xml then it only gets relative > href=filename.html for each of this book's documents. Instead > we need to know href=userdocs/concepts/filename.html > > The map:aggregate and map:part are not yet documented, so i > am not sure how they work. Is it possible that they can provide > such metadata about the document? > > A last resort approach would be to hard-code this value inside > each book.xml as an attribute of the <book> element. > > Please try the new functionality - hopefully you can see a solution. > --David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
