Component: \product, \project
Hello, when looking at http://wiki.contextgarden.net/Project_structure - - why \product and/or \project specification is used in the COMPONENT in the example, or why is it supposed or even required to use in components? I imagined that component doesn't need to know in which project/product is used, even when in may be intended to more projects/products. So does it mean I would have to enumerate all projects/products in which the component is to be used? Or can be \product and/or \project specification omitted in the component? 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 Lukáš,
I imagined that component doesn't need to know in which project/product is used, even when in may be intended to more projects/products.
Usually, projects (collections of environment files) are applied at the product level. Sometimes, however, you want to apply one at the component level, so you put a \project in the \startcomponent. You never need to put \product anywhere. Clearer descriptions of what the commands \project and \product do can be found on the command pages; same for all the other structure commands. The [[Project structure]] page is indeed confusing, it needs a better structure itself. Description from http://wiki.contextgarden.net/Command/project: When used inside a \startproduct or \startcomponent environment, \project is an instruction to source any \environment files linked in the project file. Description from http://wiki.contextgarden.net/Command/product: The command \product does not do anything: to link a product to a project file, one should use \project inside the product. Nonetheless, the \product command is often used inside project files as a reminder of what products the project involves. Hope this helps. Kind regards, Sietse
... Thanks for explanation, it's much clearer now.
Best regards,
Lukas
On Tue, 04 Sep 2012 13:57:50 +0200, Sietse Brouwer
Hello Lukáš,
Usually, projects (collections of environment files) are applied at the product level. Sometimes, however, you want to apply one at the component level, so you put a \project in the \startcomponent.
You never need to put \product anywhere.
Clearer descriptions of what the commands \project and \product do can be found on the command pages; same for all the other structure commands. The [[Project structure]] page is indeed confusing, it needs a better structure itself.
Description from http://wiki.contextgarden.net/Command/project: When used inside a \startproduct or \startcomponent environment, \project is an instruction to source any \environment files linked in the project file.
Description from http://wiki.contextgarden.net/Command/product: The command \product does not do anything: to link a product to a project file, one should use \project inside the product. Nonetheless, the \product command is often used inside project files as a reminder of what products the project involves.
Hope this helps. Kind regards, Sietse
-- 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 (2)
-
Procházka Lukáš Ing. - Pontex s. r. o. -
Sietse Brouwer