ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	"Jairo A. del Rio" <jairoadelrio6@gmail.com>
Subject: Re: How to properly pass TeX/Lua data to MetaPost/MetaFun?
Date: Sun, 9 Aug 2020 19:46:03 +0200	[thread overview]
Message-ID: <8673baf5-0390-7731-c983-1eb9e47a4165@xs4all.nl> (raw)
In-Reply-To: <CAKyqqaYCjU5z3RddbaL7Ca7gLc-YscT6a=ayEHe1k5noGe1o1w@mail.gmail.com>

On 8/9/2020 5:39 PM, Jairo A. del Rio wrote:
> Hi, list! I'm doing the following to scale squares and other stuff in 
> MetaPost/MetaFun. Although the following kinda works (maybe I'm just 
> lucky with this), I want to know how to do a better piece from it. I'm 
> concerned with passing data from Lua and TeX to Metapost and better ways 
> to do it in ConTeXt. Thank you in advance.
> 
> \starttext
> My text
> 
> \startMPinitializations
> numeric myunit;
> myunit := \the\dimexpr1em\relax;
> \stopMPinitializations
> \startluacode
> 
> userdata = userdata or {}
> userdata.dummydata = { {1, 2}, {3, 4} }
> 
> context.startMPcode()
> 
> for j=1,#userdata.dummydata do
> for i=1,#userdata.dummydata[1] do
> context("draw unitsquare scaled myunit shifted ((%d,%d)*myunit);", 
> userdata.dummydata[i][j], userdata.dummydata[i][j])
> end
> end
> 
> context.stopMPcode()
> 
> \stopluacode
> \stoptext
Something:

\starttext

\startluacode

     userdata = userdata or {}
     userdata.dummydata = { {1, 2}, {3, 4} }

     function MP.GetI()
         mp.print(#userdata.dummydata)
     end
     function MP.GetJ(i)
         mp.print(#userdata.dummydata[i])
     end
     function MP.GetIJ(i,j)
         mp.pair(userdata.dummydata[i][j],userdata.dummydata[i][j])
     end

\stopluacode

\startMPcode
     numeric myunit ; myunit := EmWidth;
     for i = 1 upto lua.MP.GetI() :
         for j = 1 upto lua.MP.GetJ(i) :
             draw unitsquare scaled myunit shifted (myunit * 
(lua.MP.GetIJ(i,j)));
         endfor ;
     endfor ;
\stopMPcode

\stoptext

There are of course also other ways but this is more educational as start.

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
___________________________________________________________________________________

  reply	other threads:[~2020-08-09 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 15:39 Jairo A. del Rio
2020-08-09 17:46 ` Hans Hagen [this message]
2020-08-09 18:03   ` Jairo A. del Rio
2020-08-09 18:05     ` Hans Hagen
2020-08-09 18:08       ` Jairo A. del Rio

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=8673baf5-0390-7731-c983-1eb9e47a4165@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=jairoadelrio6@gmail.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).