ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: new version
Date: Fri, 11 Apr 2008 09:50:14 +0200	[thread overview]
Message-ID: <115224fb0804110050m6fba7ce6q83a5b89e74c3a43a@mail.gmail.com> (raw)
In-Reply-To: <47FF15A7.9080407@wxs.nl>

On Fri, Apr 11, 2008 at 9:39 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Aditya Mahajan wrote:
> > On Fri, 11 Apr 2008, Hans Hagen wrote:
> >
> >> Hi,
> >>
> >> concerning the mplibrary in mkiv ...
> >>
> >> - it does not use the metafun mem file; when formats are generated a
> >> special mem file is made and put alongside the context format
> >>
> >> - however, this only happens when a new version is found (is the case
> >> with a new zip), or when an error is encountered in the format
> >> (compatibility issue)
> >>
> >> - in case of doubt, or when you patch metafun, you can say
> >>
> >> ctxtool --touch
> >> texexec --make
> >>
> >> i will try to make this more robust in the future
> >>
> >> the new mkiv mp graphics implementations is prepared for mixed usage,
> >> i.e. we can use multiple metapost formats; i'm still not sure about the
> >> interface, for instance:
> >>
> >> \startuseMPgraphic{metafun:bla} ...
> >>
> >> \startuseMPgraphic{mpost:bla} ...
> >>
> >> or so, more news later
> >
> > This could break existing code. I sometimes use
> > \startuseMPgraphic{system:bla} and {system:blabla} etc to distinguish all
> > "system diagrams".
>
> sure, but seldom metafun: i suppose -)
>
> > How about
> >
> > 1. \defineMPreusegraphic[useMPgraphic][format=metafun]
> >     \defineMPreusegraphic[useMPOSTgraphic][format=mpost]
> >   and then one can use \startuseMPgraphic and \startuseMPOSTgraphic.
> >
> > 2. If you have to make the label of the graphic determine the format, then
> > maybe something like
> >
> > \startuseMPgraphic{::metafun::bla} so that it does not break existing
> > code.
>
> \startuseMPgraphic[metafun]{...} is also an option but not consistent,
> unless we provide
>
> \startuseMPgraphic[optional format][name][optional settings]
>
> which i somehow dislike
>
> > 3. What about \startMPcode, \startMPpage, and \processMPbuffer? I think
> > that the first approach will be easier to adapt.
>
> another option is:
>
> \useMPformat{metafun}

\setupsystem
   [mpformat=metafun]

> (the reason for { }instead of [] is that it then can be used within []
> without extra {})

This was something i never understood in the past, the difference
between the "name" setting for buffers and MP graphics.

> yet another option is
>
> \startMPcode
>   mpformat := "metafun"
>   ...
> \stopMPcode

No.

Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-04-11  7:50 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 22:24 Hans Hagen
2008-04-11  4:33 ` Aditya Mahajan
2008-04-11  7:39   ` Hans Hagen
2008-04-11  7:50     ` Wolfgang Schuster [this message]
2008-04-11  9:48       ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2020-08-25 18:14 Hans Hagen
2020-06-10  8:02 Hans Hagen
2020-06-10 15:05 ` Alan Bowen
2005-05-25 15:34 Hans Hagen
2005-05-25 18:42 ` Taco Hoekwater
2005-05-25 19:00   ` Hans Hagen
2005-05-25 19:25     ` Taco Hoekwater
2005-05-27 15:07       ` Taco Hoekwater
2005-05-27 18:17         ` Hans Hagen
2005-05-28 18:18         ` Stuart Jansen
2005-05-25 19:26 ` Idris Samawi Hamid
2005-05-25 20:07   ` Hans Hagen
2005-05-26 21:57 ` Adam Lindsay
2005-05-26 23:29   ` Hans Hagen
2005-05-27 14:49     ` Adam Lindsay
2005-05-27 18:22       ` Hans Hagen
2005-05-27 19:09         ` Adam Lindsay
2005-05-26 23:34   ` Hans Hagen
2005-05-27 13:27     ` Adam Lindsay
2005-05-27 13:45       ` Hans Hagen
2005-05-27 18:20       ` Peter Münster
2005-05-27 18:41         ` Hans Hagen
2004-01-13 16:41 Hans Hagen
2003-09-17 17:47 Steffen Wolfrum
2003-09-17 12:25 Steffen Wolfrum
2003-09-17 16:00 ` Hans Hagen
2003-09-17 10:50 Hans Hagen
2003-08-07 16:02 Hans Hagen
2002-07-26 22:53 Hans Hagen
2002-07-27 19:34 ` Jens-Uwe Morawski
2002-07-29  7:15   ` Hans Hagen
2002-07-29  9:09     ` Jens-Uwe Morawski
2002-07-29  9:33       ` Hans Hagen
2002-07-30  9:56         ` Jens-Uwe Morawski
2002-07-30 21:06           ` Hans Hagen
2002-07-31  8:29             ` Jens-Uwe Morawski
2000-09-21 16:33 Hans Hagen
2000-01-24 11:13 Hans Hagen
2000-01-24 11:42 ` Mr. Wang Lei
2000-01-24 12:24   ` Tobias Burnus
2000-01-24 15:45     ` Hans Hagen
2000-01-24 15:32   ` Hans Hagen
2000-01-24 11:44 ` Tobias Burnus
2000-01-24 15:47   ` 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=115224fb0804110050m6fba7ce6q83a5b89e74c3a43a@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).