From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Draft version of document
Date: Wed, 8 Aug 2012 19:48:13 +0200 [thread overview]
Message-ID: <C3AC8B82-F499-4C20-913F-D4AD463CFC12@gmail.com> (raw)
In-Reply-To: <CAF=dkzzZksg0=go_2YWzjWGrMvGRwLsbdLjbuHFBVOjZJPbAww@mail.gmail.com>
Am 08.08.2012 um 17:04 schrieb Sietse Brouwer <sbbrouwer@gmail.com>:
> I'm trying to work out how to describe the new feature, so I can add
> that to the documentation. I think I see two features, but I'm not
> sure. Can you tell me if the below is correct?
>
> New feature 1: previously we could only do
> \startplacefigure[reference=fig:mill, title={A Mill}]
> or
> \startsection[reference=sec:sheep, title={The Sheep}]
>
> but now we can do
> \startplacefigure[reference=fig:mill, title={A Mill}][resource=mill]
> or
> \startsection[reference=sec:sheep, title={The Sheep}][mykey=myvalue]
>
> Nothing is done with the parameters in the second key=value list, but
> they are stored as part of the object when the object is written to
> its figures/sections/whatever list; and there they can be used in
> constructing the Table of figures/contents/whatever.
Yes, the user variables are only stored in the utility file and can be used when you print the list entries.
> New feature 2: the command
> \rawstructurelistuservariable{#1}
> . This command can be used by custom list entry macros like
> \mylistentrymacro below:
> \setuplist[somelist][alternative=command, command=\mylistentrymacro]
>
> The command gets a property from the current list entry object, like so:
> \rawstructurelistuservariable{resource} %--> mill
>
> Question: does this work, too, or can we only access values in the
> *second* key=value list?
> \rawstructurelistuservariable{reference} %--> fig:mill
The arguments you give with the first argument are processed by context before they
are written to the utility file and only three values can be used when you create your
own list layout, the user variables on the other side are written to the utility file without
any modification and whatever you write here can be used in the list.
Wolfgang
___________________________________________________________________________________
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:[~2012-08-08 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 11:18 Roger Mason
2012-08-06 16:14 ` Sietse Brouwer
2012-08-07 9:19 ` Roger Mason
2012-08-07 12:51 ` Sietse Brouwer
2012-08-07 14:37 ` Hans Hagen
2012-08-07 14:41 ` Hans Hagen
2012-08-08 15:04 ` Sietse Brouwer
2012-08-08 17:48 ` Wolfgang Schuster [this message]
2012-08-08 21:36 ` 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=C3AC8B82-F499-4C20-913F-D4AD463CFC12@gmail.com \
--to=wolfgang.schuster@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).