From: Malte Stien <malte@stien.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Simple input vs component structure
Date: Sun, 18 Sep 2016 22:26:56 +1000 [thread overview]
Message-ID: <70927CF8-FB67-40B5-8FB8-F0CDC04B8B91@stien.de> (raw)
Hi all,
I have a set of reference manuals that consist of a number of chapters. Those documents pull in the individual chapters via \input commands.
I have just recently discovered that ConTeXt actually DOES support a project/product/component structure. So, I have been experimenting with making the individual reference manuals ‘products’ and converting all chapters into ‘components’. However, I wonder what that actually gains me? What are the benefits of this product/component structure? It looks like I can reference other sections in these other components, but I can do that now even with the simple \input.
What am I missing?
Another related question in this context is: What do I actually expect when I run the project file, as in:
$ context project.tex
ConText runs for a little while, and actually states in the log somewhere
result saved in file: project.pdf, compresslevel 3, objectcompresslevel 3
but no such file is generated; it also does not build the individual components? What does it do? Or what should I expect it to do?
Thank you,
Malte
--
“The Electric Monk was a labour-saving device, like a dishwasher or a video recorder... Electric Monks believed things for you, thus saving you what was becoming an increasingly onerous task, that of believing all the things the world expected you to believe. ― Douglas Adams, Dirk Gently's Holistic Detective Agency
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2016-09-18 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70927CF8-FB67-40B5-8FB8-F0CDC04B8B91@stien.de \
--to=malte@stien.de \
--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).