ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: ConTeXt + asymptote
Date: Tue, 25 Apr 2006 10:02:23 +0200	[thread overview]
Message-ID: <444DD78F.6090307@elvenkind.com> (raw)
In-Reply-To: <444DCA0D.5080505@wxs.nl>



Hans Hagen wrote:
> 
> looks parsable

But you see only a small bit of the actual output ;-)

 From Mojca:

>>Whoever is game can start with the diff below, but I'm also not sure
>>it's worth it.  My ideal figure program:
>>
>>1. Agnostic about the tex engine (tex/latex/context), easy to integrate
>>   with any of them.  MP is good here.
>>2. 3D built in.

I've asked this to a wide range of people and have never, ever gotten an
answer that is even close to usable for development purposes:

   What is actually needed to make it easy to do 3D in MP?

>>3. Modern color models (cmyk, transparency)

cmyk color model is older.much than rgb :-)

It would not be hard to add the cmyk color space, but transparancy can 
not easily be done in PostScript output (it would require overlap
removal code, and that is not present at all).

>>4. Decent syntax.  MP is a bit ghastly, and writing macros is horrible
>>   esp. with vardefs.  I prefer a non-macro language, and asymptote is
>>   good that way
>>  

True. But then again, you do not _really_ need vardef macros.

Cheers, Taco

  reply	other threads:[~2006-04-25  8:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 15:49 Renaud AUBIN
2006-04-21 16:17 ` Renaud AUBIN
2006-04-21 16:45   ` Hans Hagen
2006-04-21 18:29     ` Jilani Khaldi
2006-04-21 18:52       ` Renaud AUBIN
2006-04-21 19:11         ` Hans Hagen
2006-04-21 19:13         ` Hans Hagen
2006-04-21 19:25           ` Renaud AUBIN
2006-04-22  8:38             ` Hans Hagen
2006-04-22  9:16               ` andrea valle
2006-04-21 19:10       ` Hans Hagen
2006-04-21 19:20         ` Renaud AUBIN
2006-04-21 19:52           ` Hans Hagen
2006-04-23 18:51             ` Renaud AUBIN
2006-04-23 20:28               ` Hans Hagen
2006-04-23 21:02                 ` Renaud AUBIN
2006-04-23 21:50                   ` Hans Hagen
2006-04-23 22:33                     ` Renaud AUBIN
2006-04-24  0:54                       ` Sanjoy Mahajan
2006-04-24  7:33                       ` Hans Hagen
2006-04-25  4:36                         ` Sanjoy Mahajan
2006-04-25  7:04                           ` Hans Hagen
2006-04-25  8:02                             ` Taco Hoekwater [this message]
2006-04-25 15:17                             ` Sanjoy Mahajan
2006-04-21 20:00         ` ConTeXt +Tioga Jilani Khaldi
2006-04-21 20:49           ` Sanjoy Mahajan
2006-04-22  7:47           ` Hans Hagen
2006-04-22  9:47             ` Taco Hoekwater
2006-04-22 12:12               ` Jilani Khaldi
2006-04-22 15:56                 ` andrea valle
2006-04-21 19:37     ` ConTeXt + asymptote Sanjoy Mahajan
2006-04-21 23:30       ` Mojca Miklavec
2006-04-25  7:52 ` Taco Hoekwater
2006-06-29 13:40 John Bowman
2006-06-29 18:05 ` Hans Hagen
2006-06-30  1:12 ` Sanjoy Mahajan
2006-06-30  8:16   ` Hans Hagen
2006-10-15  5:04 John Bowman

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=444DD78F.6090307@elvenkind.com \
    --to=taco@elvenkind.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).