On Thu, 01 Mar 2012 09:53:23 +0100, Hans Hagen wrote:
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 nee
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.
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
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 s
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
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 compo
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
\stopco
