Re: Structuring topics

Re: Structuring topics

[Vyatcheslav Yatskovsky]

Thank you, Wolfgang. I'll try to get into my tomorrow's clean head and 
wikify it. )

> What's the problem with my answer, i described differences between \def
> and \define
> and the most important one is point one, i'll show it to you in two
> examples
>
> 1. \def
>
> \starttext
> \def\hans{hans}
> \def\hans{taco}
> \hans
> \stoptext
>
> the output of this example is 'taco' because the second \def statement
> overides the first
>
> 2. \define
>
> \starttext
> \define\hans{hans}
> \define\hans{taco}
> \stoptext
>
> the output now is 'hans' because \define checks whether a command with
> the name \hans
> is already defined, if this isn't true \hans is created with the content
> 'hans' while
> in the second \define \hans is already available and nothing happens but
> you get
> a warning on the terminal
>
> system          : command \hans is already defined
>
>
> to summary this you can say \def is for developers and \define for users
> but this won't
> work in all cases because \define can't create commands with optional
> arguments :(
>
> Wolfgang


-- 
Best Regards,
Vyatcheslav Yatskovsky
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Structuring topics

[Wolfgang Schuster]

Am 19.04.10 19:08, schrieb Vyatcheslav Yatskovsky:
> Concerning \define... The answer is too witty for me, so I will leave 
> the wiki page untouched.

What's the problem with my answer, i described differences between \def 
and \define
and the most important one is point one, i'll show it to you in two examples

1. \def

\starttext
\def\hans{hans}
\def\hans{taco}
\hans
\stoptext

the output of this example is 'taco' because the second \def statement 
overides the first

2. \define

\starttext
\define\hans{hans}
\define\hans{taco}
\stoptext

the output now is 'hans' because \define checks whether a command with 
the name \hans
is already defined, if this isn't true \hans is created with the content 
'hans' while
in the second \define \hans is already available and nothing happens but 
you get
a warning on the terminal

system          : command \hans is already defined


to summary this you can say \def is for developers and \define for users 
but this won't
work in all cases because \define can't create commands with optional 
arguments :(

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
___________________________________________________________________________________

Re: Structuring topics

[Vyatcheslav Yatskovsky]

Hi Wolfgang,
> title=yes,
> titleleft=,
> titleright=,

Yeah, thanks! That's the title that makes it!


Concerning \define... The answer is too witty for me, so I will leave 
the wiki page untouched.

-- 
Best Regards,
Vyatcheslav Yatskovsky
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Structuring topics

[Wolfgang Schuster]

Am 18.04.10 21:36, schrieb Vyatcheslav Yatskovsky:
> Hello,
>
> Pardon me for another small question.
>
> I want to structure my document into topics, surrounded by start/stop, 
> numbered and with caption.
>
> I discovered that enumerations do numbering, but don't allow caption 
> to pass, and descriptions allow captions, but don't numerate.
>
> Is there a middle of these? )
>
>
> %\defineenumeration
> %[topic]
> %[text=Topic,
title=yes,
titleleft=,
titleright=,
> %inbetween=\blank,
> %after=\blank]
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
___________________________________________________________________________________

Structuring topics

[Vyatcheslav Yatskovsky]

Hello,

Pardon me for another small question.

I want to structure my document into topics, surrounded by start/stop, 
numbered and with caption.

I discovered that enumerations do numbering, but don't allow caption to 
pass, and descriptions allow captions, but don't numerate.

Is there a middle of these? )


%\defineenumeration
%[topic]
%[text=Topic,
%inbetween=\blank,
%after=\blank]

\definedescription
[topic]
[location=top,
text=Topic ,
inbetween=\blank,
after=\blank]

\starttext

\starttopic{The name of the topic}
bla
\stoptopic

\starttopic
bla-bla
\stoptopic

\stoptext


Regards,
Vyatcheslav
___________________________________________________________________________________
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
___________________________________________________________________________________