ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jannie Hofmeyr" <jhsh@iafrica.com>
Subject: Building a graph in a Context presentation
Date: Wed, 1 Dec 1999 00:39:40 +0200	[thread overview]
Message-ID: <00b801bf3b83$dd2c8460$a8c807c4@jhsh> (raw)

Dear Group

One of my applications of Context will be to create screen presentations. It
appears that the functionality to build up a list of items sequentially in
successive pages is already therev (s-pre-00.tex). What I particularly need
to
do, however, is to sequentally build up a graph with explanatory text
appearing
next to the graph as each bit is inserted (i.e., as successive stuff is
added
to the graph, an itemised list builds up next to the graph). Typically, I
produce the series of graphs with gnuplot and its metapost terminal (what a
pleasure to finally be able to do that!).

Is there a way of building text and graphics in combination in Context? I
wouldn't mind doing this manually, i.e. creating each successive page as a
separate entity. However, I then need to put the graph and the existing text
in
exactly the same place, so that I can create the illusion of a sequential
build
on a single page. This means I must avoid slight shifts in graphs and text
placing when paging.

As I understand it from art-pres.pdf and reading s-pre-00.tex, Context, when
building an itemized list, does it by successively uncovering hidden parts
of a
page. Would this be possible with a Metapost graph?

Fervently-hoping-that-my-problem-can-be-solved-ly yours
Jannie

--------------------------------
Prof. Jannie Hofmeyr
Dept. of Biochemistry, Univ. of Stellenbosch
Private Bag X1, Matieland 7602
South Africa
e-mail: jhsh@iafrica.com / jhsh@maties.sun.ac.za
tel. +27 21 808 3039
fax. +27 21 808 3022


             reply	other threads:[~1999-11-30 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-30 22:39 Jannie Hofmeyr [this message]
1999-12-01 11:52 ` Hans Hagen
1999-12-01 14:13 ` 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='00b801bf3b83$dd2c8460$a8c807c4@jhsh' \
    --to=jhsh@iafrica.com \
    /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).