allan wrote:
Per Einar Ellefsen wrote:

Suggestion:
- we only use that breadcrumb for some headers: we probably don't need them
for Level 1 headers, but we could have them for atleast level 2, and maybe
level 3 headers.
- we add a horizontal rule before the level 1 header, as to separate
sections visually.



i suggest we try and implement the bullets as breadcrumb and
visual "nesthood" for all levels > 1.
(i have enclosed a gif where the level-4 header is in italic)

instead of the horizontal rule you suggested to seperate
parent items (level1) i have enclosed a gif - a larger-sized
first-letter, just an idea.

you like?

yes, the .oO is nice.

Do you think these elements should be linked to the actual sub-sections? If we do that, there is a problem. Let's say that you click and get to the parent. How do you get back to the child? The feature works only one way.

I've a different idea. Let's have only one icon before the sub-section title which makes it easier to feel the nesting level. something like:

 ___    ___    ___
[   ]  [## ]  [###]
[___], [___], [###], etc

where each image shows the deepness.

But hey, why don't we use the numbers? like we have in the pdf version? That would be the simplest and most intuitive way to go:

3.1.4
1.1.1.7

===

I agree with Per Einar that enlarging the first letter is not the best idea. Usually this technique works well when you have a phrase which is already all upcased.

I still suggest that we need to stick to similar to the default definition of <H*> where the real size varies.

--


_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to