ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tobias Wolf <towolf@gmail.com>
Subject: Re: Sparklines to be in ConTeXt?
Date: Mon, 1 Aug 2005 12:34:38 +0200	[thread overview]
Message-ID: <e06bd0fe050801033421a73cc@mail.gmail.com> (raw)
In-Reply-To: <4.3.1.2.20050731135018.0251eee0@cits1.stanford.edu>

>The particular temptation that I saw was that they _aren't_ a substitute
>for a full graph -- they're only a substitute for the information one gets
>were trying to put so much information in them that one would need to spend
>time studying them to read them, and that misses the point.

> Personally, I haven't yet written anything that seemed to provide a good
> use for them, so I'm sort of waiting to have a real opinion on them until I
> actually find a place to give them a proper try-out in a "real-world"
> situation.
> 
> In any case, I do agree that MetaPost is probably one of the best ways to
> implement them, and ConTeXt's MetaPost integration should make it quite
> easy to organize such implementations.

To clarify, my question wasn't a request or anything. I see it in the
same position as you, a toy used in exploration of some concepts that
nonetheless seem to be based on some valid points. One of them being
that the data and the text shouldn't be too disparate, floated far
afield,  and another that the content to presentation ratio should be
maximal. These Sparklines cannot replace a full-blown figure but
afford to approach data more in the sense of reading than in the sense
of deciphering.

I asked here because everything about it screamed ConTeXt (also
considering that the favourite command here seems to be \input tufte).
Thought this meme must have infected some here.
- Tobias

  reply	other threads:[~2005-08-01 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 20:47 Tobias Wolf
2005-07-31 21:11 ` Brooks Moses
2005-08-01 10:34   ` Tobias Wolf [this message]
2005-08-01 12:34     ` Hans Hagen
2005-07-31 21:32 ` Hans Hagen

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

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

  git send-email \
    --in-reply-to=e06bd0fe050801033421a73cc@mail.gmail.com \
    --to=towolf@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).