From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: metafun 2
Date: Wed, 14 Aug 2019 11:54:54 +0200 [thread overview]
Message-ID: <174f2ea4-37ef-046c-198b-a9c7b3912e4a@xs4all.nl> (raw)
Hi,
In the process of providing an additional (more abstract) interface to
some of the old and also new MetaFun code we wonder what kind of
features users would like to see.
http://www.pragma-ade.com/general/magazines/mag-1104-mkiv.pdf
As a teaser I uploaded a MyWay document that shows some of what is
coming. All is experimental but it shows the direction. We're talking
ConTeXt LMTX here. For instance,
draw lmt_outline [
content = "hello",
kind = "reverse",
fillcolor = "darkred",
drawcolor = "darkblue",
rulethickness = 1/2,
] ysized h shifted (3.75h,-1.25h) ;
Wraps all the outline drawing in one macro with a set of options (there
will be xml interface definitions for that). Or take:
draw lmt_followtext [
content = "How well does it work {\bf 1}! ",
path = (fullcircle scaled 4cm),
trace = true,
spread = true,
] ysized 5cm ;
which is an easier interface to text along a curve. Arrows can be drawn
with
draw lmt_arrow [
kind = "draw",
location = "middle",
alternative = "curved",
path = fullcircle
scaled 3cm
shifted (3.5cm,0cm),
] withcolor "darkblue" ;
but of course the low level interface with its many variables for
tweaking stays around. Other examples are shown in the mentioned document.
So the question is: What do you miss in metapost support? Of course it
should fit within the concept, so 'artistic freehand drawings' is not
something that is likely to get interfaced. We are particularly
interested in educational applications, if only because ConTeXt started
out that way.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-08-14 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 9:54 Hans Hagen [this message]
2019-08-14 10:18 ` Henri Menke
2019-08-14 11:16 ` Hans Hagen
2019-08-14 11:31 ` Floris van Manen
2019-08-14 11:53 ` Hans Hagen
2019-08-15 6:05 ` Arthur Reutenauer
2019-08-14 14:22 ` Otared Kavian
2019-08-14 14:49 ` Hans Hagen
2019-08-14 14:53 ` Aditya Mahajan
2019-08-14 14:58 ` Otared Kavian
2019-08-14 15:11 ` Wolfgang Schuster
2019-08-14 15:34 ` Hans Hagen
2019-08-14 14:58 ` Mikael P. Sundqvist
2019-08-14 15:37 ` Hans Hagen
[not found] ` <CAHy-LL9D5NB6qZYj+QynCWR-rqk6suD3reepLUgO8KOwrjwnXA@mail.gmail.com>
2019-08-19 19:20 ` Fwd: " Mikael P. Sundqvist
2019-08-16 23:31 ` Adam Reviczky
2019-08-17 1:27 ` Alan Braslau
2019-08-17 8:52 ` Hans Hagen
2019-08-17 18:12 ` Adam Reviczky
2019-08-19 19:15 ` Jorge Manuel
2019-09-08 8:42 ` Aditya Mahajan
2019-09-08 10:09 ` Otared Kavian
2019-09-08 14:54 ` Aditya Mahajan
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=174f2ea4-37ef-046c-198b-a9c7b3912e4a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).