ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jilani Khaldi <jilani.khaldi1@virgilio.it>
Subject: Re: ConTeXt +Tioga
Date: Sat, 22 Apr 2006 14:12:18 +0200	[thread overview]
Message-ID: <444A1DA2.7040302@virgilio.it> (raw)
In-Reply-To: <4449FBAA.2030305@elvenkind.com>


>It is just my 2c, but I really dislike the Tioga approach. It feels
>like typesetting a book in TeX by writing a single-shot pascal
>program. ;-)
>
>Specifically, I find code like this (Tioga):
>
>   move_to_point(x0, y0)
>   append_curve_to_path(x1, y1, x2, y2, x3, y3)
>
>far uglier than this (Asymptote/MetaPost):
>
>   z0.. controls z1 and z2 .. z3
>
>  
>
Very true, but you forgot that in Tioga everything is done inside Ruby 
interpreter. Tioga is a Ruby extension so you could use the power of 
Ruby, its standard library and all the other extensions made for it 
inside Tioga.
However, I don't like Asymptote, just seeing things like this:
----------------------
struct parent {
real x=1;
public void virtual(int) {write (0);}
void f() {virtual(1);}
}
parent operator init() {return new parent;}
void write(parent p) {write(p.x);}
struct child {
parent parent;
real y=2;
void virtual(int x) {write (x);}
parent.virtual=virtual;
void f()=parent.f;
}
parent operator cast(child child) {return child.parent;}
child operator init() {return new child;}
parent p;
child c;
write(c); // Outputs 1;
p.f(); // Outputs 0;
c.f(); // Outputs 1;
write(c.parent.x); // Outputs 1;
write(c.y);
---------------
But, do we really need a baroque language like this to just draw some 
primitive graphics?

jk

--
Jilani KHALDI
http://jkhaldi.oltrelinux.com

  reply	other threads:[~2006-04-22 12:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 15:49 ConTeXt + asymptote 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
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 [this message]
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

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=444A1DA2.7040302@virgilio.it \
    --to=jilani.khaldi1@virgilio.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).