From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Pstricks and Asymptote
Date: Tue, 17 Nov 2009 10:29:59 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.0911171013450.14253@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <3b4b12310911161457s37d837eic14397ebe823b5a2@mail.gmail.com>
On Mon, 16 Nov 2009, Curiouslearn wrote:
> Mojca, in case you read this, can you please let me know what the
> status on asymptote is.
I am not Mojca, but I'll comment on this anyways :)
I looked into integrating asymptote this summer (spent around a month
going to asymptote macro code). Asymptote works fine with mkiv, if you use
asymptote in a stand alone mode. Getting asymptote to run within context
is easy or extremely difficult; depending on how you look at it.
If one wants to set everything the asymptote way, and simply want
\startASYcode
...
\stopASYcode
to copy its content to its file, create a asymptote figure and insert it
in context, that is easy. You just need to tweak three lines of m-r.tex
and you are done (m-r.tex is around 15 lines only). But that means that
the user is responsible for setting all the fonts on his own (using
asymptote syntax).
To be at par with metapost, we should have \startASYenvironment to set the
fonts, \startASYinclusions to define macros, and then \startASYcode to
create figures; maybe also have \defineASYgraphic (need to set
OverlayWidth etc.) and \defineASYreusablegraphic. Ideally, we should also
have the equivalent of \sometxt, but after going through asymptote code, I
gave up on that (establishing a two way communication between asymptote and
context is difficult).
Most of the above is easy (in terms of implementation); but one needs to
understand asymptote and context to implement them. I did not completely
understand the low level asymptote code, so after a while, integrating
asymptote got low on my priorities. Maybe someone else should look at it
seriously.
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-11-17 15:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 14:12 curiouslearn
2009-11-16 14:29 ` Thomas A. Schmitz
2009-11-16 14:43 ` Alan BRASLAU
2009-11-16 22:57 ` Curiouslearn
2009-11-17 7:13 ` Alan BRASLAU
2009-11-17 13:40 ` Curiouslearn
2009-11-17 13:55 ` Henning Hraban Ramm
2009-11-17 14:29 ` Curiouslearn
2009-11-17 14:40 ` luigi scarso
2009-11-17 15:30 ` Hans Hagen
2009-11-17 15:52 ` luigi scarso
2009-11-17 16:07 ` Hans Hagen
2009-11-17 15:06 ` Alan BRASLAU
2009-11-17 15:10 ` luigi scarso
2009-11-17 15:29 ` Aditya Mahajan [this message]
2009-11-17 16:54 ` Mojca Miklavec
2009-11-17 17:25 ` Hans Hagen
2009-11-17 18:03 ` Mojca Miklavec
2009-11-18 13:45 ` Hans Hagen
2009-11-18 16:10 ` Alan BRASLAU
2009-11-18 16:19 ` luigi scarso
2009-11-18 17:08 ` Alan BRASLAU
2009-11-18 17:16 ` luigi scarso
2009-11-18 17:31 ` Peter Münster
2009-11-18 20:23 ` luigi scarso
2009-11-18 20:49 ` Hans Hagen
2009-11-19 8:07 ` Mojca Miklavec
2009-11-18 20:34 ` luigi scarso
2009-11-17 22:12 ` Wolfgang Schuster
2009-11-18 15:31 ` luigi scarso
2009-11-16 14:36 ` luigi scarso
2009-11-17 16:57 ` Mojca Miklavec
2009-11-17 17:01 ` Mojca Miklavec
2009-11-17 17:05 ` luigi scarso
2009-11-17 17:22 ` Hans Hagen
2009-11-17 18:21 ` Mojca Miklavec
2009-11-17 19:35 ` Curiouslearn
2009-11-17 19:59 ` Mojca Miklavec
2009-11-17 20:20 ` Curiouslearn
2009-11-17 21:46 ` Hans Hagen
2009-11-17 17:22 ` 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=alpine.LNX.2.01.0911171013450.14253@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).