Mailing List Archive: ModPerl: Docs-dev

prev/next widgets

Index | Next | Previous | View Threaded

domm at zsi

Dec 27, 2001, 10:24 AM

Post #1 of 4 (858 views)
Permalink

prev/next widgets

Hi!

I was just playing around with the prev/up/next and TOC/TOP stuff.

I like Allans idea, but I felt something was wrong, and I think I now know
what was giving me troubles:

In the Prev/Up/Next thing, Up is written on grey (or blue, can't tell on my
laptop..), while Prev/Next is written on white.

In the Top-Thing, the same desing (grey box, next to a white box) is used
for a different meaning (both links go to the TOP), which is very confusing.

My Suggestion:
in the Prev/Up/Next Widget, drop the UP link. It's not really needed here,
as the breadcrumb allready provides a link UP. Then use the idea of the TOP
widget (Grey Box with arrow, then text) for the prev/next widget, maybe even
splitting it in two parts. You can look at a /very/ crude implementation at
http://domm.zsi.at/modperl-site-domm/navbarlocal.html
Just imagine proper arrow images instead of ASCII art and a box around the
text instead of the grey background...

--
D_OMM +----> http://domm.zsi.at <-----+
O_xyderkes | neu: Arbeitsplatz |
M_echanen | http://domm.zsi.at/d/d162.html |
M_asteuei +--------------------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl

stas at stason

Dec 27, 2001, 10:32 AM

Post #2 of 4 (796 views)
Permalink

Re: prev/next widgets [In reply to]

Thomas Klausner wrote:

> Hi!
>
> I was just playing around with the prev/up/next and TOC/TOP stuff.
>
> I like Allans idea, but I felt something was wrong, and I think I now know
> what was giving me troubles:
>
> In the Prev/Up/Next thing, Up is written on grey (or blue, can't tell on my
> laptop..), while Prev/Next is written on white.
>
> In the Top-Thing, the same desing (grey box, next to a white box) is used
> for a different meaning (both links go to the TOP), which is very confusing.
>
> My Suggestion:
> in the Prev/Up/Next Widget, drop the UP link. It's not really needed here,
> as the breadcrumb allready provides a link UP.

I disagree to drop the UP link (may be it should be called differently?
"parent"?). This is why:

The breadcrumb is useful for:
- global navigation
- knowing where you are.

A quick go to the parent link is very helpful to be in the vicinity of
its children. You have to scroll up for breadcrumb, what if you are
located at the bottom of a very long page? I think this last reason is
the most important.

> Then use the idea of the TOP
> widget (Grey Box with arrow, then text) for the prev/next widget, maybe even
> splitting it in two parts. You can look at a /very/ crude implementation at
> http://domm.zsi.at/modperl-site-domm/navbarlocal.html
> Just imagine proper arrow images instead of ASCII art and a box around the
> text instead of the grey background...

So may be we should drop the idea having two items in the same nav
widget contrasting each other? And just have something like:

------------------------
[ < Prev | UP | Next > ]
------------------------

We always have 2 or 3 elements so we don't really have to use the
technique used when you have many rows or columns.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl

domm at zsi

Dec 30, 2001, 2:13 PM

Post #3 of 4 (795 views)
Permalink

Re: prev/next widgets [In reply to]

Hi!

On Fri, Dec 28, 2001 at 01:32:37AM +0800, Stas Bekman wrote:
> I disagree to drop the UP link (may be it should be called differently?
> "parent"?). This is why:
>
> The breadcrumb is useful for:
> - global navigation
> - knowing where you are.
>
> A quick go to the parent link is very helpful to be in the vicinity of
> its children. You have to scroll up for breadcrumb, what if you are
> located at the bottom of a very long page? I think this last reason is
> the most important.
That's true. I did't thought about that.

What I don't like about "UP" is that prev and next aren't labeled "prev" and
"next" but with the titles of the corresponding documents. So you have a
mixture of lables (named ones and generic) which is sort of iritating. What
about using the name of the "UP" document in the widget?
Or using literally "prev | up | next" (although I like the idea of knowing
what "next" will be)

> So may be we should drop the idea having two items in the same nav
> widget contrasting each other? And just have something like:
>
> ------------------------
> [ < Prev | UP | Next > ]
> ------------------------
>
> We always have 2 or 3 elements so we don't really have to use the
> technique used when you have many rows or columns.
I don't get you here ...

--
D_OMM +----> http://domm.zsi.at <-----+
O_xyderkes | neu: Arbeitsplatz |
M_echanen | http://domm.zsi.at/d/d162.html |
M_asteuei +--------------------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl

stas at stason

Dec 30, 2001, 9:26 PM

Post #4 of 4 (802 views)
Permalink

Re: prev/next widgets [In reply to]

Thomas Klausner wrote:

> Hi!
>
> On Fri, Dec 28, 2001 at 01:32:37AM +0800, Stas Bekman wrote:
>
>>I disagree to drop the UP link (may be it should be called differently?
>>"parent"?). This is why:
>>
>>The breadcrumb is useful for:
>>- global navigation
>>- knowing where you are.
>>
>>A quick go to the parent link is very helpful to be in the vicinity of
>>its children. You have to scroll up for breadcrumb, what if you are
>>located at the bottom of a very long page? I think this last reason is
>>the most important.
>>
> That's true. I did't thought about that.
>
> What I don't like about "UP" is that prev and next aren't labeled "prev" and
> "next" but with the titles of the corresponding documents. So you have a
> mixture of lables (named ones and generic) which is sort of iritating. What
> about using the name of the "UP" document in the widget?
> Or using literally "prev | up | next" (although I like the idea of knowing
> what "next" will be)

That's easy to do. But the problem that it takes a lot of space (e.g.
'mod_perl developer's guide', so the 3 cells won't fit into one line
almost for sure (they are not always fitting anyway, but it's nice when
they are). May be we should replace Up with some other symbolic meaning?
'Contents'? But then it can be confused with TOC. 'Parent'? 'Level Up'?

"prev" and "next" aren't as nice, especially since we have the knowledge
of the real names.

I suggest replacing 'Up' with an icon. So we have 3 cells with 3 icons:
<|^|>, but in addition, cells 1 and 3 have the titles.

>>So may be we should drop the idea having two items in the same nav
>>widget contrasting each other? And just have something like:
>>
>>------------------------
>>[ < Prev | UP | Next > ]
>>------------------------
>>
>>We always have 2 or 3 elements so we don't really have to use the
>>technique used when you have many rows or columns.
>>
> I don't get you here ...

When you present many rows or columns:

foo bar foo bar
bar foo bar foo
foo foo foo foo

usually alternate rows (or cols) are coloured into a different color. I
was saying that we don't have to do that, because we have only three.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads