categories - Category Theory list
 help / color / mirror / Atom feed
From: Jeremy Gibbons <Jeremy.Gibbons@comlab.ox.ac.uk>
To: <categories@mta.ca>
Subject: Re: graphics
Date: Sun, 29 Feb 2004 11:49:11 +0000 (GMT)	[thread overview]
Message-ID: <Pine.GSO.4.33.0402291141440.8294-100000@mercury.comlab> (raw)
In-Reply-To: <200402250526.i1P5Q8gA007761@coraki.Stanford.EDU>

On Tue, 24 Feb 2004, Vaughan Pratt wrote:

> If you're a Picasso in such things then
> starting off with xfig isn't so bad, but if you're more of a Mondrian you
> might prefer to work in Latex's picture environment from the get-go.
> ...
> The only other widely supported language I know that's expressive enough to
> write a complete macro library in 20 lines for capabilities like flowcharts,
> digital or analog circuits, and lattice diagrams and that interoperates
> smoothly with Latex is PostScript.

I'm surprised no-one seems to have mentioned John Hobby's METAPOST
language. This is a mostly declarative language, with the capability of
solving linear equations. (So you can, for example, express that one item
appears halfway between two others, and that relationship will be
maintained as either endpoint moves.) It also integrates beautifully with
LaTeX. If you're neither a Picasso nor a Mondriaan, but you like writing
programs, I would have said this was the tool for you. Should come with
any decent TeX distribution.

Jeremy






  parent reply	other threads:[~2004-02-29 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  5:26 graphics Vaughan Pratt
2004-02-27 16:44 ` graphics Robert Seely
2004-02-28 10:15   ` graphics: comment and a query Ronald  Brown
2004-02-29 11:49 ` Jeremy Gibbons [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-27 23:48 graphics Valeria.dePaiva
2004-02-21 16:57 graphics jim stasheff
2004-02-23  2:20 ` graphics David Yetter

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=Pine.GSO.4.33.0402291141440.8294-100000@mercury.comlab \
    --to=jeremy.gibbons@comlab.ox.ac.uk \
    --cc=categories@mta.ca \
    /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).