ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: handling key=value sets with lua
Date: Sun, 9 Jan 2011 23:43:00 +0100	[thread overview]
Message-ID: <AANLkTinNQr70seOLQM-OrL9HYCkBgs9__EonXPnBmhq5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimD=F0V9vzTdT-4LuEDPhQWtZh=YisYAj2quvZW@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2046 bytes --]

On Sun, Jan 9, 2011 at 11:13 PM, Philipp A. <flying-sheep@web.de> wrote:

> hi list,
>
> skip to the many %%% if you just want to help me ;)
>
> i need to make a macro which consists of ten optional arguments. it
> wouldn’t be too ugly to require to write the following to use it, since it
> outputs a 3×3 matrix with an adjacent tenth item, but tex can’t handle ten
> arguments afaik.
>
>
> syntax idea:
> empty:
> \bigcrafting%
> {}{}{}%
> {}{}{}{}%
> {}{}{}%
>
> partly filled:
> \bigcrafting%
> {}{}{}%
> {planks}{planks}{}{workbench}%
> {planks}{planks}{}%
>
> how it should look:
> [image: CraftingWorkbenchIO.png]
>
> ok, since using empty “required” arguments aren’t elegent, either, i wanted
> to get into key=value sets, but ran into the next problem:
>
> i wanted to instead define bigcrafting to work like this:
> \bigcrafting
>   [21=planks, 22=planks,
>    31=planks, 32=planks]
>   [workbench]
>
> but \getparameters<http://wiki.contextgarden.net/Commands_with_KeyVal_arguments>can’t handle numerical values.
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> As Hans wrote it's possible, but I like the to use "row" for row, "col" for
column and "c" for cell
i.e
\def\BigCrafting[#1]%
{\getparameters[Ph][c11={},c12={},c13={},
c21={},c22={},c23={},c24={},
c31={},c32={},c33={},#1]
\bTABLE
\bTR\bTD\getvalue{Phc11}\eTD\bTD\getvalue{Phc12}\eTD\bTD\getvalue{Phc13}\eTD\eTR
\bTR\bTD\getvalue{Phc21}\eTD\bTD\getvalue{Phc22}\eTD\bTD\getvalue{Phc23}\eTD\bTD\getvalue{Phc24}\eTD\eTR
\bTR\bTD\getvalue{Phc31}\eTD\bTD\getvalue{Phc32}\eTD\bTD\getvalue{Phc33}\eTD\eTR
\eTABLE
}
\starttext
\BigCrafting[c11=FOO,c33=GOO,c22=BOO,c24=Zoo]
\BigCrafting[c11=FOO,c24=GOO]
\stoptext

You can also use a better namespace
\def\BigCrafting[#1]%
\unprotect
\getparameters[flying-sheep@web.de:][c11={},c12={},c13={},
c21={},c22={},c23={},c24={},
c31={},c32={},c33={},#1]
\getvalue{flying-sheep@web.de:c11}%%
\getvalue{flying-sheep@web.de:c12}%% and so on
\protect
}

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2914 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2011-01-09 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 22:13 Philipp A.
2011-01-09 22:24 ` Hans Hagen
2011-01-09 22:41   ` Philipp A.
2011-01-09 22:43 ` luigi scarso [this message]

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=AANLkTinNQr70seOLQM-OrL9HYCkBgs9__EonXPnBmhq5@mail.gmail.com \
    --to=luigi.scarso@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).