From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: ntg-context@ntg.nl
Subject: Re: Project, product, component...
Date: Tue, 28 Feb 2012 18:24:55 +0100 [thread overview]
Message-ID: <4F4D0DE7.9010705@gyza.cz> (raw)
In-Reply-To: <op.waeds3gbtpjj8f@lpr>
Hello,
Project structure use quite often, but yet similar question not occurred
to me. I had always previously PPP and CCC as existing filenames on the
disk. I suppose it would be right.
But I would like to extend Luke's question on this issue:
You can load an existing component to other components? Is it acceptable
or undesirable? At some point I would throw this possibility, but I do
not want to do something that could then backfire somehow.
Thanx Jaroslav Hajtmar
Dne 28.2.2012 17:37, Procházka Lukáš Ing. - Pontex s. r. o. napsal(a):
> Hello,
>
> I'm trying to use advantages of project/product/component structure.
>
> Suppose having a very simple example (both files in the same directory):
>
> ---- Prod.mkiv
> \startproduct PPP
> \component Comp.mkiv
>
> Product
> \stopproduct
> ----
>
> And:
>
> ---- Comp.mkiv
> \startcomponent CCC
> Component
> \stopcomponent
> ----
>
> When I compile Comp.mkiv, I get (successfully) text "Component".
>
> When I compile Prod.mkiv, I get (successfully) text "Product Component".
>
> So the question - what are "PPP" and "CCC" identifiers (following
> \startproduct and \starcomponent respectively) used or intended for?
>
> - So far, it seems to me that I refer to file names (as with \input)
> when working with components rather than their ids assigned by
> \startcomponent or \startproduct.
>
> What would be a situation when I'd need to use ids "CCC" or "PPP" (or
> later, those assigned by "\startproduct PROD" and "\startenvironment
> ENV")?
>
> Best regards,
>
> Lukas
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-28 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 16:37 Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-28 17:24 ` Jaroslav Hajtmar [this message]
2012-02-28 18:01 ` Marco
2012-02-28 18:18 ` Jaroslav Hajtmar
2012-03-01 8:30 ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-03-01 8:53 ` Hans Hagen
2012-03-02 7:25 ` Procházka Lukáš Ing. - Pontex s. r. o.
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=4F4D0DE7.9010705@gyza.cz \
--to=hajtmar@gyza.cz \
--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).