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 Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
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
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} (the reason for { }instead of [] is that it then can be used within [] without extra {}) yet another option is \startMPcode mpformat := "metafun" ... \stopMPcode and parse for it, but that has other disadvantages; anyhow ... more thinking needed ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Fri, Apr 11, 2008 at 9:39 AM, Hans Hagen
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
Wolfgang Schuster wrote:
This was something i never understood in the past, the difference between the "name" setting for buffers and MP graphics.
the mp related commands are low level commands, there was never a high level interface to it (using [] etc) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Aditya Mahajan -
Hans Hagen -
Wolfgang Schuster