From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: How to get parameters in lua
Date: Fri, 19 Sep 2014 10:03:15 +0200 [thread overview]
Message-ID: <541BE343.9040709@wxs.nl> (raw)
In-Reply-To: <CAO8LnPHg0+S=3BSHnND10OigDjYhtNu8XvTN19F6Sj4WGqmZ+Q@mail.gmail.com>
On 9/19/2014 9:30 AM, Christoph Reller wrote:
> Hi,
>
> \installcommandhandler nicely provides (among others) \define<name> and
> \setup<name> commands. Thus it is easy to provide a key with
> \setup...[key=value] and to read the value of such a key with
> \<name>parameter{key}.
>
> My question is: How do I read the value of a key defined with
> \setup...[key=value] on the lua side? If I use
> context.<name>parameter("key")
> then the value of key is printed directly. I want to be able to read
> that value and use it in lua with something like
> myvariable = context.?whatfunction?("key")
>
> Here is some example code:
>
> \unprotect
>
> \startluacode
> function myfun(parameters,content)
> context("From lua: Parameters: ")
> context(parameters)
> context.elemparameter("gkey") -- directly prints the parameter
> context.par()
> end
> \stopluacode
>
> \installnamespace{elem}
> \installcommandhandler \????elem {elem} \????elem
> \appendtoks
> \setuevalue{\currentelem}{\elem_cmd{\currentelem}}%
> \to \everydefineelem
>
> \unexpanded\def\elem_cmd#environment{%
> \edef\currentelem{#environment}%
> \dosingleempty\elem_cmd_parameters}
>
> \def\elem_cmd_parameters[#parameters]#content{%
> \setupcurrentelem[#parameters]
> From \TeX\: Parameters: key=\elemparameter{key},
> gkey=\elemparameter{gkey}\par
>
> \ctxlua{myfun(\!!bs#parameters\!!es,\!!bs\normalunexpanded{#content}\!!es)}
> }
>
> \defineelem[base]
> \setupelem[gkey=gval]
>
> \protect
>
> \starttext
>
> \base[key=val]{Hello}
>
> \stoptext
>
> Thank you for any feedback,
something like this ... keep in mind that there is no grouping in lua
% macros=mkvi
\unprotect
\installnamespace{elem}
\installcommandhandler \????elem {elem} \????elem
\startluacode
userdata.elem = { data = { [""] = { } } }
function userdata.elem.define(namespace,parent)
print("define",namespace,parent)
userdata.elem.data[namespace] = { }
if namespace ~= parent then
table.setmetatableindex(userdata.elem.data[namespace],userdata.elem.data[parent])
end
end
function userdata.elem.setup(namespace,key,gkey)
print("setup",namespace,key,gkey)
userdata.elem.data[namespace].key = key
userdata.elem.data[namespace].gkey = gkey
end
function userdata.myfun(namespace,one,two)
context.par()
context("elem: one=%s",userdata.elem.data[namespace][one])
context.par()
context("elem: two=%s",userdata.elem.data[namespace][two])
context.par()
end
\stopluacode
\appendtoks
\setuevalue{\currentelem}{\elem_cmd{\currentelem}}%
\ctxlua{userdata.elem.define("\currentelem","\currentelemparent")}%
\to \everydefineelem
\appendtoks
\ctxlua{userdata.elem.setup("\currentelem","\elemparameter{key}","\elemparameter{gkey}")}%
\to \everysetupelem
\unexpanded\def\elem_cmd#environment%
{\edef\currentelem{#environment}%
\dosingleempty\elem_cmd_parameters}
\def\elem_cmd_parameters[#parameters]#content%
{\setupelem[\currentelem][#parameters]
From \TeX\: Parameters: key=\elemparameter{key},
gkey=\elemparameter{gkey}\par
\ctxlua{userdata.myfun("\currentelem","key","gkey")}}
\defineelem[base]
\setupelem[gkey=gval]
\protect
\starttext
\base[key=val]{Hello}
\stoptext
A simpler alternative is:
% macros=mkvi
\unprotect
\installnamespace{elem}
\installcommandhandler \????elem {elem} \????elem
\startluacode
userdata.elem = { data = { } }
function userdata.elem.sync(key,gkey)
userdata.elem.data.key = key
userdata.elem.data.gkey = gkey
end
function userdata.myfun(one,two)
context.par()
context("elem: one=%s",userdata.elem.data[one])
context.par()
context("elem: two=%s",userdata.elem.data[two])
context.par()
end
\stopluacode
\appendtoks
\setuevalue{\currentelem}{\elem_cmd{\currentelem}}%
\to \everydefineelem
\unexpanded\def\elem_cmd#environment%
{\edef\currentelem{#environment}%
\dosingleempty\elem_cmd_parameters}
\unexpanded\def\elem_sync
{\ctxlua{userdata.elem.sync("\elemparameter{key}","\elemparameter{gkey}")}}
\def\elem_cmd_parameters[#parameters]#content%
{\setupcurrentelem[#parameters]
\elem_sync
From \TeX\: Parameters: key=\elemparameter{key},
gkey=\elemparameter{gkey}\par
\ctxlua{userdata.myfun("key","gkey")}}
\defineelem[base]
\setupelem[gkey=gval]
\protect
\starttext
\base[key=val]{Hello}
\stoptext
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-09-19 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 7:30 Christoph Reller
2014-09-19 8:03 ` Hans Hagen [this message]
2014-09-20 12:45 Christoph Reller
2014-09-21 11:04 ` 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=541BE343.9040709@wxs.nl \
--to=pragma@wxs.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).