From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: graph module metapost
Date: Tue, 06 Aug 2002 14:06:52 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020806140105.01fb5cd0@server-1> (raw)
In-Reply-To: <20020806131651.08fb6f86.morawski@gmx.net>
At 01:16 PM 8/6/2002 +0200, Jens-Uwe Morawski wrote:
>On Tue, 06 Aug 2002 11:20:51 +0200
>Hans Hagen <pragma@wxs.nl> wrote:
>
> >
> > The next release will provide a (more efficient) module:
> >
> > \usemodule[graph]
>
>Since \usemodule is used for diffent modules TeX (bib) or MP (graph)
>it has to know, that 'graph' is a MP module.
actually, it does not load an mp module, it only adds the right
initialization code to let mp load the module
>What setup is needed to load own MP moduls using \usemodule?
>I think \definefilesynonym is not enough.
>
>is there something like:
>
>\defineMPmodule[Boxes][boxes.mp]
>\usemodule[Boxes]
normally
\startMPinclusions
input boxes
\stopMPinclusions
should be ok; a more general scheme (something loadMPmodule) is only needed
when we also have to do a lot of related context interfacing (like with
graph, where these is this text along axis stuff)
When we run into more modules, we can set up a system for that, but first
we need to get a clear picture of demands;
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
prev parent reply other threads:[~2002-08-06 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 9:20 Hans Hagen
2002-08-06 11:16 ` Jens-Uwe Morawski
2002-08-06 12:06 ` Hans Hagen [this message]
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=5.1.0.14.1.20020806140105.01fb5cd0@server-1 \
--to=pragma@wxs.nl \
--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).