unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>,
	politza@hochschule-trier.de, Tassilo Horn <tsdh@gnu.org>
Subject: Re: Displaying scrollable images in a grid-layout
Date: Wed, 15 Apr 2015 10:17:02 +0600	[thread overview]
Message-ID: <CAP_d_8VrqTw1Yh6Z0we6hNmLnMrNf6ZR89T9q2JAdxa5iaPR5g@mail.gmail.com> (raw)
In-Reply-To: <831tjmazgz.fsf@gnu.org>

On Wed, Apr 15, 2015 at 8:37 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> ??? Why does it make sense to show a partial line, when we can show it
> in its entirety?  Can you explain?

You assume that the line is a bigger unit than the image, that the
image is part of the line. However, in PDF viewers, an image of a
whole page contains many lines of text.

Many people, when confronted with a need to read documents in PDF
format, scroll the parts they have already read past the top window
edge, so that the window edge tracks where they are reading. This way,
if they are distracted, they can continue reading immediately without
having to find the last sentence they read.

The UI gesture for such reading mode is either mouse scrolling or
pressing the <down> arrow repeatedly or continuously. In both cases,
the reader wants scrolling to be as smooth as possible, ideally, with
each press or each wheel step scrolling by a constant number of
pixels. (Mouse scrolling may be further improved with acceleration,
but also based on pixels, not logical lines.)



  reply	other threads:[~2015-04-15  4:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  8:06 Displaying scrollable images in a grid-layout Andreas Politz
2015-04-13 14:57 ` Eli Zaretskii
2015-04-13 19:35   ` Andreas Politz
2015-04-13 20:27     ` Eli Zaretskii
2015-04-14 13:29       ` Tassilo Horn
2015-04-14 14:11         ` Stefan Monnier
2015-04-14 14:43           ` Tassilo Horn
2015-04-14 20:04             ` Stefan Monnier
2015-04-14 22:15               ` Rasmus
2015-04-14 14:51         ` Eli Zaretskii
2015-04-14 19:24           ` Tassilo Horn
2015-04-15  2:37             ` Eli Zaretskii
2015-04-15  4:17               ` Yuri Khan [this message]
2015-04-15 16:05                 ` Eli Zaretskii
2015-04-15 16:35                   ` Yuri Khan
2015-04-15 16:47                     ` Eli Zaretskii
2015-04-15 17:02                       ` Yuri Khan
2015-04-15 17:33                         ` Eli Zaretskii
2015-04-15 18:26                           ` Andreas Politz
2015-04-15 19:31                           ` Stefan Monnier
2015-04-14 14:56       ` Eli Zaretskii
2015-04-14 19:29         ` Andreas Politz
     [not found]         ` <8738424igv.fsf@hochschule-trier.de>
2015-04-15  2:41           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP_d_8VrqTw1Yh6Z0we6hNmLnMrNf6ZR89T9q2JAdxa5iaPR5g@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=politza@hochschule-trier.de \
    --cc=tsdh@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).