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".
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.
3. What about \startMPcode, \startMPpage, and \processMPbuffer? I think
that the first approach will be easier to adapt.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
