You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Joshua Slive <jo...@slive.ca> on 2002/11/09 20:41:22 UTC

expanding the bread-crumbs

Attached is a patch to allow individual xml documents to add another level
to the breadcrumb links at the top of the page using the <parentdocument
href="...">...</parentdocument> tag.  It also maps this document to the
"back" link.

Some weaknesses of this approach:

1. It allows only a single extra level of breadcrumbs.  Nesting is not
supported.

2. It requires a direct link to the .html file, so if we ever change file
extensions or go with xml/html negotiation it will need to be changed in
each file.

3. It ignores the directory structure and requires explicit links in the
xml file.  (Actually, I consider this an advantage more than a weakness.
The directory structure does not necessarily map very well to the content
structure.)

All of the above problems could be fixed at the expense of added
complexity.  But I'm a huge fan of simplicity, and I think this works
"well enough".

Comments/Suggestions?

Joshua.

Re: expanding the bread-crumbs

Posted by André Malo <nd...@perlig.de>.
* Joshua Slive wrote:

> Attached is a patch to allow individual xml documents to add another level
> to the breadcrumb links at the top of the page using the <parentdocument
> href="...">...</parentdocument> tag.  It also maps this document to the
> "back" link.

+1.

Just a typo, I guess:

--- vhosts/name-based.xml	5 Oct 2002 23:12:22 -0000	1.3
+++ vhosts/name-based.xml	9 Nov 2002 19:39:29 -0000
@@ -4,7 +4,7 @@

 <manualpage>
 <relativepath href=".."/>
-
+<parentdocument href="../">Virtual Hosts</parentdocument>
 <title>Name-based Virtual Host Support</title>

the href has to be a "./" ;-)

> 1. It allows only a single extra level of breadcrumbs.  Nesting is not
> supported.

I think, if we need nested parentdocuments some day, then we'll create it.

> 2. It requires a direct link to the .html file, so if we ever change file
> extensions or go with xml/html negotiation it will need to be changed in
> each file.

since we're actually doing this currently with all explicit links, it's not 
really a problem, I think. We can remove or replace the .html extentsions 
with xslt, if we want to do so.

> All of the above problems could be fixed at the expense of added
> complexity.  But I'm a huge fan of simplicity, and I think this works
> "well enough".

+1 again.

nd
-- 
"Die Untergeschosse der Sempergalerie bleiben währenddessen aus
 statistischen Gründen geflutet." -- Spiegel Online

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org