Re: [NTG-context] Product-component structure

2016-07-11 Thread Alan BRASLAU
On Mon, 11 Jul 2016 13:01:58 +0200 Procházka Lukáš Ing. wrote: > - Single components can be compiled successfully, too; sections here > are NOT NUMBERED as in the final document. A nagging question that I have always had about structure is that it would be rather nice if compiling a component th

Re: [NTG-context] Product-component structure

2016-07-11 Thread Procházka Lukáš Ing .
Hello, my "how-I-do-it" used for typesetting a large book was: styles.sty % Styles, settings etc.; never compiled individually, thus ".sty"; the file also doesn't use '\startenvironment' ... '\stopenvironment' commands (I even don't know whether such commands exist; anyway, I didn't need

Re: [NTG-context] Product-component structure

2016-06-26 Thread Hans Hagen
On 6/25/2016 7:13 PM, Wolfgang Schuster wrote: Hans Hagen 25. Juni 2016 um 11:56 i always use one main environment (that can include others) and putting an \environment on top of a component is then not much overhead (compared to getting the content done) The problem wit

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
On Sat, 25 Jun 2016, Wolfgang Schuster wrote: Hans Hagen 25. Juni 2016 um 11:56 i always use one main environment (that can include others) and putting an \environment on top of a component is then not much overhead (compared to getting the content done) The problem w

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
On Sat, 25 Jun 2016, Wolfgang Schuster wrote: Aditya Mahajan 25. Juni 2016 um 18:37 On Sat, 25 Jun 2016, Hans Hagen wrote: So, to a newcomer, one can suggest to simply use components and environments. What is the advatange of the extra structure provided by product

Re: [NTG-context] Product-component structure

2016-06-25 Thread Wolfgang Schuster
Hans Hagen 25. Juni 2016 um 11:56 i always use one main environment (that can include others) and putting an \environment on top of a component is then not much overhead (compared to getting the content done) The problem with puttins \environment before \startcomponents

Re: [NTG-context] Product-component structure

2016-06-25 Thread Wolfgang Schuster
Aditya Mahajan 25. Juni 2016 um 18:37 On Sat, 25 Jun 2016, Hans Hagen wrote: So, to a newcomer, one can suggest to simply use components and environments. What is the advatange of the extra structure provided by product/project? A product is the book itself while com

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
On Sat, 25 Jun 2016, Hans Hagen wrote: So, what's the recommended alternative? One could move the \environment to the components, but that can lead to a lot of repetitions (if there are many environments). i always use one main environment (that can include others) and putting an \environment

Re: [NTG-context] Product-component structure

2016-06-25 Thread Hans Hagen
On 6/25/2016 10:42 AM, Aditya Mahajan wrote: On Sat, 25 Jun 2016, Wolfgang Schuster wrote: Aditya Mahajan 24. Juni 2016 um 21:19 Hi, This is based on a question on tex.sx: http://tex.stackexchange.com/q/316504/323 In file-job.lua, we have: local processors = utilit

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
On Sat, 25 Jun 2016, Wolfgang Schuster wrote: Aditya Mahajan 24. Juni 2016 um 21:19 Hi, This is based on a question on tex.sx: http://tex.stackexchange.com/q/316504/323 In file-job.lua, we have: local processors = utilities.storage.allocate { ... [v_product]

Re: [NTG-context] Product-component structure

2016-06-24 Thread Wolfgang Schuster
Aditya Mahajan 24. Juni 2016 um 21:19 Hi, This is based on a question on tex.sx: http://tex.stackexchange.com/q/316504/323 In file-job.lua, we have: local processors = utilities.storage.allocate { ... [v_product] = { [v_text]= { "many", process

Re: [NTG-context] Product-component structure

2016-06-24 Thread Hans Hagen
On 6/24/2016 9:19 PM, Aditya Mahajan wrote: Hi, This is based on a question on tex.sx: http://tex.stackexchange.com/q/316504/323 In file-job.lua, we have: local processors = utilities.storage.allocate { ... [v_product] = { [v_text]= { "many", processfilemany },

[NTG-context] Product-component structure

2016-06-24 Thread Aditya Mahajan
Hi, This is based on a question on tex.sx: http://tex.stackexchange.com/q/316504/323 In file-job.lua, we have: local processors = utilities.storage.allocate { ... [v_product] = { [v_text]= { "many", processfilemany }, [v_project] = { "once", processfileonce }