From: "luigi.scarso" <luigi.scarso@logosrl.it>
Subject: Re: XYpic
Date: Fri, 29 Apr 2005 09:08:45 +0200 [thread overview]
Message-ID: <4271DD7D.40701@logosrl.it> (raw)
In-Reply-To: <42715E34.5090804@seznam.cz>
Vit, many thanks for your answer.
Vit Zyka wrote:
> 1. For a moment I set
> shell_escape = f
> in `kpsewhich texmf.cnf'
>
ok, done
> 2. Input file f.tex:
> \startuseMPgraphic{A}
> draw unitcircle scaled\overlaywidth;
> \stopuseMPgraphic
>
> \defineoverlay
> [B]
> [\uniqueMPgraphic{A}]
>
> \starttext
> \framed[background=B]{Hallo frame!}
> \stoptext
>
> 3a. classical run
> texexec --pdf f
>
No circle under frame, right? If not, I have a bad installation; please
discard the rest
(and some hints to repair will be really appreciate :) ).
> 3b. step by step
> texexec --pdf --nomp f
> mpost f-mpgraph
> texexec --pdf --nomp f
>
>
A circle appear under the frame. But I have 3 runs ( texexec, mpost,
texexec).
Now, what is my goal ?
To achieve a circle under the frame as quick as possible.
For 3.a, in f.log I find
mpost -progname=mpost -mem=metafun f-mpgraph
system()...disabled.
An attempt to run mpost failed: no circle, goal unsatisfied.
For 3.b, I run manually mpost (and then again texexec): goal satisfied.
With shell_export=t, 3.a) is ok, but f.log says
system(mpost -progname=mpost -mem=metafun f-mpgraph)...executed.
So it seems that my goal can be achieved only with a run of mpost.
With XYPic, a similar result can be achieved without mpost:
%%
%% WARNING:: deprecated example
%% Don't use it !
%%
\input xy
\xyoption{frame}
\starttext
\xy
(0,0) *++=\hbox{\framed{Hallo frame}} *\frm{o} ;
\endxy
\stoptext
Of course this doesn't mean that XY is better/worse than mpost, nor that
using mpost coupled with context will be always slow than others ways;
but sometimes a faster alternative may be required.
Sure for XYPic, name spaces collisions, cpu/memory required, syntax are
(some) items
to consider: but it also comes with a bunch of features and may be
faster than mpost
in some circumstances.
[OT] XFIG: fig2dev can be export to metapost and in multi-metapost.
Hence, from the moon, I see that xfig can be used with context.
luigi
next prev parent reply other threads:[~2005-04-29 7:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 15:45 Rif: Re: dotted line for \framed ? Luigi Scarso
2005-04-26 15:35 ` luigi.scarso
2005-04-26 18:24 ` XYpic (was: dotted line for \framed ?) Henning Hraban Ramm
2005-04-27 10:18 ` XYpic Vit Zyka
2005-04-28 8:01 ` XYpic luigi.scarso
2005-04-28 10:42 ` XYpic Vit Zyka
2005-04-28 11:02 ` XYpic luigi.scarso
2005-04-28 22:05 ` XYpic Vit Zyka
2005-04-29 7:08 ` luigi.scarso [this message]
2005-04-29 8:21 ` XYpic Vit Zyka
2005-04-29 10:27 ` XYpic luigi.scarso
2007-04-27 12:46 XYPic Dirard Mikdad
2007-05-01 6:55 ` XYPic luigi scarso
2007-05-01 7:09 ` XYPic luigi scarso
2007-05-01 9:18 ` XYPic Dirard Mikdad
2007-05-01 19:45 ` XYPic luigi scarso
2007-05-02 8:14 ` XYPic Dirard Mikdad
2007-05-02 8:57 ` XYPic luigi scarso
2007-05-02 14:20 ` XYPic Dirard Mikdad
2007-05-02 15:05 ` XYPic luigi scarso
2007-05-02 15:16 ` XYPic Dirard Mikdad
2007-05-02 16:31 ` XYPic luigi scarso
2007-05-03 6:39 ` XYPic luigi scarso
2007-05-04 0:17 ` XYPic luigi scarso
2007-05-04 12:57 ` XYPic Dirard Mikdad
2007-05-04 13:25 ` XYPic luigi scarso
2007-05-14 9:33 ` XYPic luigi scarso
2007-05-15 12:40 ` XYPic Dirard M. Mikdad
2007-04-27 12:49 Xypic Dirard Mikdad
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=4271DD7D.40701@logosrl.it \
--to=luigi.scarso@logosrl.it \
--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).