ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: Environments, Projects, Products, Components
Date: Wed, 30 May 2001 20:01:58 +0200	[thread overview]
Message-ID: <25874768.20010530200158@bigfoot.com> (raw)
In-Reply-To: <3B150E38.6060605@elvenkind.com>

Wednesday, May 30, 2001 Taco Hoekwater wrote:

TH> Giuseppe Bilotta wrote:

>> Hello,
>> 
>> I'm getting the first attempts to structured ConTeXt, and I needed
>> some clarifications.
>> 
>> As I see it, it goes like this:
>> 
>> environments are more or less the equivalent of LaTeX2e classes.
>> 
>> Projects are collection of material (say, Calculus books)
>> 
>> Products are the single books (say, Calculus, Advanced Calculus)
>> 
>> Components are the single chapters of the various books.

TH> Correct.

Phew! :-)

>> Shouldn't I change chapfoo.tex so that it says \product bookb?

TH> Just delete the \product line alltogether, it is optional. :-)

Oh.

TH> Or you can do it like this:

TH> chapfoo.tex:

TH> ...
TH> \product booka
TH> \input chapfoo-contents
TH> ...

TH> chapbar.tex:
TH> ....
TH> \product bookb
TH> \input chapfoo-contents
TH> ...

I see. Hadn't thought of that ... which do you think is the better
idea? taking \product off is space-saving (only one file per
chapter, instead of two wrappers plus the file), but somehow seems
less structuring ... maybe I'd better keep \product in until I
need to use the same file somewhere else ...

What happens if product booka meets a component that says \product
bookb?

--
Giuseppe "Oblomov" Bilotta


  reply	other threads:[~2001-05-30 18:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 11:40 Giuseppe Bilotta
2001-05-30 15:14 ` Taco Hoekwater
2001-05-30 18:01   ` Giuseppe Bilotta [this message]
2001-05-31  7:51     ` Taco Hoekwater
2001-05-31  9:34       ` Hans Hagen
2001-08-30 17:54         ` Steve Lumos
2001-08-31  7:19           ` Hans Hagen
2001-05-31  8:11     ` Re[2]: " Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2002-05-25 18:14 Broken catcodes Giuseppe Bilotta
2002-05-25 20:17 ` Hans Hagen
2002-05-25 21:46   ` Re[2]: " Giuseppe Bilotta
2002-05-26 17:39     ` Hans Hagen
2002-05-26 20:38       ` Re[3]: " Giuseppe Bilotta
     [not found]       ` <pragma@wxs.nl>
2001-03-12 16:50         ` fonts fonts and fonts Hans Hagen
2001-03-12 17:07           ` Frans Goddijn
2001-03-12 23:11           ` Christoph Dreyer
2001-03-13  9:33             ` S2P development
2001-03-13 10:12               ` Han The Thanh
2001-03-13 10:35               ` Hans Hagen
2001-03-14 21:32               ` H. Ramm
2001-03-13  7:12           ` Steve Lumos
2001-03-13  9:13             ` Hans Hagen
2001-03-14  0:29             ` Uwe Koloska
2001-03-13 14:35           ` Ed L Cashin
2001-03-14  0:18           ` Uwe Koloska
2001-03-15 21:55           ` H. Ramm
2002-05-27 15:27         ` Re[2]: Broken catcodes Daniel Flipo
2002-05-27 15:32           ` Hans Hagen
2001-02-22  7:24 Horizontal centering \startlines...\stoplines Steve Lumos
2001-02-22  8:47 ` Horizontal centering \startlines...\stoplines / poems Hans Hagen
2001-03-03  9:22   ` Steve Lumos
2001-03-04 21:09     ` Hans Hagen
2001-03-07  4:08       ` Steve Lumos
2001-03-07  8:14         ` Hans Hagen
2000-08-19 12:21 Setting up footnotes Joop Susan
2000-08-21 11:00 ` Hans Hagen
2000-08-21 18:19   ` Joop Susan
2000-08-22  6:59     ` 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=25874768.20010530200158@bigfoot.com \
    --to=bourbaki@bigfoot.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).