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 -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038
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 ___________________________________________________________________________________
On 2012-02-28 Jaroslav Hajtmar
Project structure use quite often, but yet similar question not occurred to me.
It's a very interesting question, I was asking myself the same and I'm curious about the answer. The ConTeXt magazine #1101 - Project Structure¹ is reserved about this topic and simply states: “The names given after the start command are not that important…”
I had always previously PPP and CCC as existing filenames on the disk.
I always used filenames, too.
But I would like to extend Luke's question on this issue: You can load an existing component to other components?
The ConTeXt magazine #1101 includes a table of the possible combinations of the commands. From this table I conclude that components are allowed between: ∙ \starttext \stoptext ∙ \startcomponent \stopcomponent ∙ \startproduct \stopproduct Marco [1] http://pragma-ade.com/general/magazines/mag-1101.pdf
Thanx Marco. I remember that I once read that magazine, but I already forgot it. It is good that you reminded me. It is good to occasionally return to the forgotten manuals. Thanks again. Jaroslav. Dne 28.2.2012 19:01, Marco napsal(a):
On 2012-02-28 Jaroslav Hajtmar
wrote: Project structure use quite often, but yet similar question not occurred to me.
It's a very interesting question, I was asking myself the same and I'm curious about the answer. The ConTeXt magazine #1101 - Project Structure¹ is reserved about this topic and simply states:
“The names given after the start command are not that important…”
I had always previously PPP and CCC as existing filenames on the disk.
I always used filenames, too.
But I would like to extend Luke's question on this issue: You can load an existing component to other components?
The ConTeXt magazine #1101 includes a table of the possible combinations of the commands. From this table I conclude that components are allowed between:
∙ \starttext \stoptext ∙ \startcomponent \stopcomponent ∙ \startproduct \stopproduct
Marco
[1] http://pragma-ade.com/general/magazines/mag-1101.pdf
___________________________________________________________________________________ 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 ___________________________________________________________________________________
Hello,
as no new answer so far, I started to experiment.
It seems that [at least] component id(s) cannot be omitted:
---- Prod.mkiv
\startproduct % PPP
\component Comp.mkiv
Product
\stopproduct
----
And:
---- Comp.mkiv
\startcomponent % CCC
%\product Prod
%\project Proj
Component
\stopcomponent
----
- Gives a wrong product, as Prod.pdf doesn't include the component.
Another test:
---- Prod.mkiv
\startproduct _ % PPP
\component Comp.mkiv
\component Comp2.mkiv
Product
\stopproduct
----
And:
---- Comp.mkiv
\startcomponent _ % CCC
Component
\stopcomponent
----
---- Comp2.mkiv
\startcomponent _ % CCC
Component2
\stopcomponent
----
Gives a good result.
So it seems that [at least some] ids are required, and just not-to-be-empty.
I tested the case when all product/component ids were the same, i.e. "_", as a dummy value.
As later the ids are referred nowhere, it seems that they are necessary just due to syntactical rules.
Or - ?
Lukas
On Tue, 28 Feb 2012 19:01:52 +0100, Marco
On 2012-02-28 Jaroslav Hajtmar
wrote: Project structure use quite often, but yet similar question not occurred to me.
It's a very interesting question, I was asking myself the same and I'm curious about the answer. The ConTeXt magazine #1101 - Project Structure¹ is reserved about this topic and simply states:
“The names given after the start command are not that important…”
I had always previously PPP and CCC as existing filenames on the disk.
I always used filenames, too.
But I would like to extend Luke's question on this issue: You can load an existing component to other components?
The ConTeXt magazine #1101 includes a table of the possible combinations of the commands. From this table I conclude that components are allowed between:
∙ \starttext \stoptext ∙ \startcomponent \stopcomponent ∙ \startproduct \stopproduct
Marco
[1] http://pragma-ade.com/general/magazines/mag-1101.pdf
___________________________________________________________________________________ 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 ___________________________________________________________________________________
-- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038
On 1-3-2012 09:30, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Hello,
as no new answer so far, I started to experiment.
It seems that [at least] component id(s) cannot be omitted:
the tags are (an always will be) mandate
I tested the case when all product/component ids were the same, i.e. "_", as a dummy value.
As later the ids are referred nowhere, it seems that they are necessary just due to syntactical rules.
they are also used in - cross document referencing (component processing) - logging and reporting - keeping track of loading environments once - internal pusp/pop states and hashes - whatever we need in the future (so, naming all environments _ will load only one) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 01 Mar 2012 09:53:23 +0100, Hans Hagen
the tags are (an always will be) mandate
they are also used in
- cross document referencing (component processing) - logging and reporting - keeping track of loading environments once - internal pusp/pop states and hashes - whatever we need in the future
(so, naming all environments _ will load only one)
Hans
... OK, thanks for the explanation. Best regards, Lukas -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038
participants (4)
-
Hans Hagen
-
Jaroslav Hajtmar
-
Marco
-
Procházka Lukáš Ing. - Pontex s. r. o.