emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Alexander Poslavsky <alexander.poslavsky@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: css link colors for Worg are difficult to spot
Date: Sat, 6 Apr 2013 12:53:02 -0500	[thread overview]
Message-ID: <CA+M2ft-xGgdp_x7kHL54F7of0p1G+So32aa3aDVnurG0FozvBg@mail.gmail.com> (raw)
In-Reply-To: <9A40604F-1E04-414F-82BD-7699D39428CE@gmail.com>

On Sat, Apr 6, 2013 at 3:23 AM, Alexander Poslavsky
<alexander.poslavsky@gmail.com> wrote:
> On 1 Apr 2013, at 15:14, John Hendy <jw.hendy@gmail.com> wrote:
> I find the links difficult to spot in Worg sometimes, especially
> depending on monitor angle and current brightness setting. Is this an
> issue for anyone else?
> I fiddled around in /style/worg.css a bit and didn't land on anything
> too great. I'm wondering if anyone with a design background might have
> suggestions for link colors? I guess if no one else is affected by
> this... I'll just deal with it and mine sweep wildly with my mouse
> when I think a link should be in there somewhere :)
> In the old days lines used to be underlined, nowadays it is considered a bit
> dated, but an underlined item in a sentence is generally understood to be a
> link.
> A good example is http://docs.webplatform.org/wiki/html/elements/a
> Which uses:
> a { text-decoration: underline }
> and for external links:
> a.external {
> padding-right: 15px;
> margin-right: 5px;
> background-image: url(skins/webplatform/images/link-external.png);
> background-repeat: no-repeat;
> background-position: right 3px;
> }

I wouldn't mind this at all. Or perhaps the same color link, but
unvisited is underlined and visited is not? Or reddish + underline for
unvisited, greenish + underline for visited, and hover simply
brightens up each respective color or something?

> Design as this won't do on behance or dribble, but worg is primarily for
> documentation. Usability and readability should trump superficial aesthetics
> in a case like this.

Agreed as well. It drives me crazy to have posted to the list a couple
times recently for someone to tell me where, exactly, something is
only to find out there was, indeed, a link in the paragraph I was
looking at but didn't see it!


  parent reply	other threads:[~2013-04-06 17:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 13:14 css link colors for Worg are difficult to spot John Hendy
2013-04-03  9:45 ` Bastien
2013-04-03 10:20   ` Christian Moe
2013-04-03 10:47     ` Vincent Beffara
2013-04-03 10:57       ` Bastien
2013-04-04  0:05         ` John Hendy
2013-04-04  9:56           ` Bastien
2013-04-04  7:40         ` Achim Gratz
2013-04-05 23:11           ` Bastien
2013-04-06  8:23 ` Alexander Poslavsky
2013-04-06  8:28   ` Gmane orgmode down? Bastien
2013-04-06  8:46     ` Christian Moe
2013-04-06  9:35       ` Bastien
2013-04-06 17:53   ` John Hendy [this message]
2013-04-06 17:59     ` css link colors for Worg are difficult to spot Bastien
2013-04-15 19:55       ` John Hendy
2013-04-16  6:28         ` Bastien

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=CA+M2ft-xGgdp_x7kHL54F7of0p1G+So32aa3aDVnurG0FozvBg@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=alexander.poslavsky@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).