Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Christoph, all,

Christoph Noack schrieb:
Hi Bernhard, hi all!

Am Freitag, den 21.01.2011, 17:36 +0100 schrieb Bernhard Dippold:
Hi Klaus-Jürgen, Christian, all

klaus-jürgen weghorn ol schrieb:
Hi Christian,
Am 20.01.2011 01:38, schrieb Christian Lohmaier:
Hi Klaus-Jürgen, *,

On Fri, Jan 14, 2011 at 8:04 AM, klaus-jürgen weghorn ol
<ol@sophia-louise.de>  wrote:
Am 13.01.2011 21:48, schrieb Christian Lohmaier:
On Mon, Jan 10, 2011 at 3:21 PM, klaus-jürgen weghorn ol
<ol@sophia-louise.de>  wrote:
["back to top" link like on the limesurvey site]
And if so, at what position?
Lower right as limesurvey site?

I think the position is quite good. It is moved away from the text
but will
follow if you change the width of your browser.

I added it to the pumbaa site as a demo - what do you think?
http://pumbaa.documentfoundation.org:7780/ (scroll down a little, the
link will appear)
If your monitor is too big and display the whole page at once, try
http://pumbaa.documentfoundation.org:7780/get-help/mailing-lists/ -
that one is longer .-))

As there were no negative comments would you put this on the live-site?
So we can avoid "on the top" inside the texts.

+1

+/-1 :-)

Sorry, I've missed this discussion a bit. I like the general idea
(although shorter pages are attractive as well), but the current
realization might miss the main advantage. Three thoughts ...

Position: If you put it at the lower right, the mouse travel distance
will be maximized. Since we miss the advantages of Fitts's Law (lower
right browser window doesn't equal lower right screen), the very next
thing after "go top" is to use the website menu at the top.

I'm not quite sure - as the website menu is still there, people can use it without moving to the top of the page.

In my eyes the <go to the top> button will be used re-read some details or use links in the current page after reading the content partially or in a whole, but I might be wrong.

Mapping: Going up is usually located at the top (like the scrollbar
button) - the positional mapping is incorrect.

I understood Karl-Heinz differently - he used an example from Limesurvey (http://www.limesurvey.org), but this doesn't mean that they do it properly.

I found a website giving more information about the "to top" link:
http://www.cs.tut.fi/~jkorpela/www/totop.html

Self-explanation: People will have to read the text to understand the
item (and it needs to be translated?). And, the shape doesn't provide
additional clues (direction).

An (additional) arrow would be nice, but I don't know if it really works without any textual explanation.


So my proposal (if technically feasible): How about an element that
shows an arrow (up), which is located approx. 50 ... 100px next to the
LibO header (right of the header), at the top of the page.

------------------------------------------------------------------
           +----------------------------------------+  +----+
           |   HEADER HEADER HEADER HEADER HEADER   |  | /\ |
           |                                        |  +----+

I would understood this as a link back to the parent level in the navigation hierarchy. And showing / hiding it when the page is scrolled down might be disruptive.

What do you think of adding the link (not more prominent than at the moment) with an additional upward arrow at the right *upper* corner of the text area - directly below the navbar?

Best regards

Bernhard

PS: Concerning Fitt's law I don't know if we need to make this button more visible and larger. As people know where to click when they want to scroll up (upper arrow besides the website's content area), they will look at this position to place the mouse. As they already focus on a small area, they will probably see the tiny and not very colorful link. (As always - only my personal PoV, so Christoph's expertize is rated much higher...)

--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.