ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Stuart Jansen <sjansen@gurulabs.com>
Subject: Re: Necessary and optional comands for combinedcontent.
Date: Wed, 08 Jun 2005 11:16:00 -0600	[thread overview]
Message-ID: <1118250960.8901.19.camel@localhost.localdomain> (raw)
In-Reply-To: <200506080933.18491.john@wexfordpress.com>


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

On Wed, 2005-06-08 at 09:33 +0000, John R. Culleton wrote:
> There exist levels of commands:
> \definecombinedlist
> \setupcombinedlist
> 
> They seem to have similar options. Are both required? If I
> define the list fully in \definecombinedlist what purpose does 
> \setupcombined list serve in the ordinary case of a Table of
> Contents?
> 
> A related question: can I place all the necessary parameters in
> the \completecontent command and do without the other two
> completely?

ConTeXt already has the content combinedlist defined. So yes, you can
just use \completecontent[option=value]. \definecombinedlist is
available so that you can define your own type of combinedlist in case
the behavior of content does not match your needs.

The \setupcommand and \command pairing is a standard ConTeXt idiom. A
common usage is to define global behavior in the \setupcommand before
\starttext and then apply local variations in the \command.  Of course,
\setupcommand can usually be called at any time, for example to change
behavior between part one and part two of a book.

If you haven't already, I suggest looking at cont-eni.pdf for more
information. I like to make simple test cases and play with commands to
understand them better. Below is an example you could use if needed.

\starttext
\completecontent
%\completecontent[alternative=a]
%\setupcombinedlist[content][alternative=c]\placecontent
%\setupinteraction[state=start]\placecontent[interaction=all]
\chapter{One}
\section{foo}
\input tufte
\chapter{Two}
\section{bar}
\input tufte
\stoptext


-- 
Stuart Jansen <sjansen@gurulabs.com>
Guru Labs, L.C.

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2005-06-08 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  9:33 John R. Culleton
2005-06-08 17:16 ` Stuart Jansen [this message]
2005-06-08 14:48   ` John R. Culleton

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=1118250960.8901.19.camel@localhost.localdomain \
    --to=sjansen@gurulabs.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).