From: David Wooten <dw@trichotomic.net>
Subject: Re: Charts, Graphs, Tufte, and ConTeXt
Date: Fri, 21 Jul 2006 12:22:12 -0700 [thread overview]
Message-ID: <44C12964.9080303@trichotomic.net> (raw)
In-Reply-To: <6faad9f00607211036v155d27bch8003d49d667d3075@mail.gmail.com>
Mojca Miklavec wrote:
>> Thus I'm curious as to what others use... is R an efficient method to
>> produce elegant charts? Is straight MetaPost preferable?
>>
>
> With metapost you can surely achive most beautiful results and it is
> not as difficult to learn as TeX-programming. Of course you might need
> more time to draw what you need or to write your own set of macros,
> but if you have high demands about quality this might be the way to
> go.
>
> However, if you prefer doing it quicly using the existing tools (be
> aware that you have to learn how to use those tools as well), R or
> gnuplot might be an interesting choice. You'll be limited by the power
> of those two tools, but in most cases they should suffice for the
> normal usage.
>
> The gnuplot module is still in development (I've been just begging
> Hans for help a few hours ago ;). Take a look at the demo section of
> gnuplot (http://gnuplot.sourceforge.net/demo_4.1/) to see if it can
> offer you what you want to do. In that case ask on the list again,
> I'll give you further pointers how to use it with ConTeXt
> (http://pub.mojca.org/gnuplot).
>
> But basically you can take any program to draw graphs and include the
> resulting PDFs. I'm afraid that the macros from the paper which you
> pointed to, use some PostScript code that cannot be handled as-is (you
> need some conversion to PDF first) and I'm affraid that the effort put
> into making it work woudn't pay off now that you have a great varienty
> of other plotting programs, including metapost itself (esp. if the
> package has never been released - you'll probably hardly get any
> support for it).
>
> Mojca
>
Thanks very much for your reply. Your advice seems strong, and in truth
I have been intrigued by MetaPost for many years. This certainly seems a
valid excuse to delve into it ;)
David
next prev parent reply other threads:[~2006-07-21 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 16:55 David Wooten
2006-07-21 17:36 ` Mojca Miklavec
2006-07-21 19:22 ` David Wooten [this message]
2006-07-22 14:00 ` John R. Culleton
2006-07-22 15:35 ` Hans Hagen
2006-07-23 17:48 ` Sanjoy Mahajan
2006-07-23 20:04 ` Idris Samawi Hamid
2006-07-23 20:38 ` Sanjoy Mahajan
2006-07-24 9:30 ` Hans Hagen
2006-07-24 15:23 ` Sanjoy Mahajan
2006-07-25 12:12 ` Karl Ove Hufthammer
2006-07-26 21:02 ` Nicolas Grilly
2006-07-27 14:14 ` Karl Ove Hufthammer
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=44C12964.9080303@trichotomic.net \
--to=dw@trichotomic.net \
--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).