Necessary and optional comands for combinedcontent.

Necessary and optional comands for combinedcontent.

[John R. Culleton]

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

John Culleton

Re: Necessary and optional comands for combinedcontent.

[Stuart Jansen]

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

Re: Necessary and optional comands for combinedcontent.

[John R. Culleton]

On Wednesday 08 June 2005 05:16 pm, Stuart Jansen wrote:
>
> 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.


My copy of cont-enp.pdf is nearly worn out. But it does not
distinguish between necessary and optional. Hence my question. I
will try stuffing all the parameters into \completecontent and
see how far I get.

 TFYH

John Culleton