ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tree charts
Date: Wed, 21 Feb 2007 13:18:10 -0500 (EST)	[thread overview]
Message-ID: <alpine.WNT.0.82.0702211310290.2652@nqvgln> (raw)
In-Reply-To: <op.tn3y2mjznx1yh1@walayah-main>

On Wed, 21 Feb 2007, Idris Samawi Hamid wrote:

> Dear cabal,
>
> Do any of you have any examples of tree charts done in, say, MetaFun? Are
> there any macros, libraries etc. for easy tree charts in \ConTeXt?
>
> Example:
> http://www.mathematik.uni-kl.de/~anne/Aufl-Bilder/D7Tree.jpg

There are three ways you can do it in ConTeXt

1) Most features: pstricks (yes pstricks can be used with context, but 
you always have to go the ps->pdf route)

2) Easiest syntax and prettiest looking output: tikz. You need one of 
the recent versions of tikz that work fine with context (except some 
of the exotic features, like adding arbitrary nodes to the page)

3) A very flexible system, but it takes a while to get used to the 
syntax: Metaobj. You also need a workabound to get metaobj to run 
correctly with metafun (search the mailing list for Taco's 
reply on a mail with metaobj in the subject)

For things like this, my personal recommendation will be tikz. It is 
not as powerful as metapost, since all the calculations are done in 
tex, but the user interface is slightly easier to use than metapost, 
and it has a good looking library of functions.

If you need something, quick and dirty, plain metapost with boxes 
package will also work. There is also the flowchart module, but I do 
not think that it can draw diagonal lines.

Aditya

  reply	other threads:[~2007-02-21 18:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 17:05 Idris Samawi Hamid
2007-02-21 18:18 ` Aditya Mahajan [this message]
2007-02-21 19:05   ` Idris Samawi Hamid
2007-02-21 20:16     ` Idris Samawi Hamid
2007-02-21 20:45       ` Aditya Mahajan
2007-02-22  8:30         ` Hans Hagen
2007-02-22 16:52           ` Idris Samawi Hamid
2007-02-22 19:39             ` Aditya Mahajan
2007-02-22 21:13               ` debian tikz module plink
2007-02-22 22:19                 ` Aditya Mahajan
2007-02-23 10:37                   ` [NTG-context] " Johan Sandblom
2007-02-23 18:22                     ` Aditya Mahajan
2007-02-23 19:27                       ` Johan Sandblom
2007-02-23 19:28                       ` plink
2007-02-23 20:51                       ` [NTG-context] " Frank Küster
2007-02-24 16:05                         ` Ralf Stubner
2007-02-26  8:31                           ` Bug#394613: " Frank Küster
2007-02-26 10:29                             ` Johan Sandblom
2007-02-26 11:33                               ` Frank Küster
2007-02-23  1:34               ` tree charts Idris Samawi Hamid
2007-02-23  9:26             ` Hans Hagen
2007-02-23 21:45             ` David Wooten
2007-02-21 21:09       ` Hans Hagen
2007-02-21 23:13         ` quick question David C. Walden
2007-02-21 22:18           ` Aditya Mahajan
2007-02-25  0:24   ` tree charts John R. Culleton

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=alpine.WNT.0.82.0702211310290.2652@nqvgln \
    --to=adityam@umich.edu \
    --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).