mkiv: way to signal extra run(s)

mkiv: way to signal extra run(s)

[Peter Rolf]

Hi,

just wondering. Is there a official way to signal ConTeXt from a module,
that an extra run is needed?

I started thinking about adding bookkeeping for the created run time
graphics. Graphic related changes can then be detected and, if
necessary, extra runs can be started to update the changed graphics.

I need the second run to create and start the ImageMagick batch script,
but the collected info in the *.tuc file prevents ConTeXt from starting
a second/third run. Currently I use a batch file that simply deletes the
*.tuc file and then calls 'context'. As there is no bookkeeping, all the
graphics are recreated then.


Peter
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: mkiv: way to signal extra run(s)

[Philipp Gesang]

[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]

···<date: 2012-09-29, Saturday>···<from: Peter Rolf>···

> Hi,
> 
> just wondering. Is there a official way to signal ConTeXt from a module,
> that an extra run is needed?

Hi Peter, some time ago I got this answer from Hans:
http://www.mail-archive.com/ntg-context@ntg.nl/msg45820.html
(Today the table is “job.variables.tobesaved”.)

Hth
Philipp

> 
> I started thinking about adding bookkeeping for the created run time
> graphics. Graphic related changes can then be detected and, if
> necessary, extra runs can be started to update the changed graphics.
> 
> I need the second run to create and start the ImageMagick batch script,
> but the collected info in the *.tuc file prevents ConTeXt from starting
> a second/third run. Currently I use a batch file that simply deletes the
> *.tuc file and then calls 'context'. As there is no bookkeeping, all the
> graphics are recreated then.
> 
> 
> Peter
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: mkiv: way to signal extra run(s)

[Peter Rolf]

Am 29.09.2012 16:24, schrieb Philipp Gesang:
> ···<date: 2012-09-29, Saturday>···<from: Peter Rolf>···
> 
>> Hi,
>>
>> just wondering. Is there a official way to signal ConTeXt from a module,
>> that an extra run is needed?
> 
> Hi Peter, some time ago I got this answer from Hans:
> http://www.mail-archive.com/ntg-context@ntg.nl/msg45820.html
> (Today the table is “job.variables.tobesaved”.)
>
Hi Philipp,

that should work. I was planing to save the graphic hash data (id-> file
name) as lua file anyway and make use of that data in the following runs
(compare new and old hash). Storing a checksum of that file should be
all I need then.

Thanks for your help :-)

Peter


> Hth
> Philipp
> 
>>
>> I started thinking about adding bookkeeping for the created run time
>> graphics. Graphic related changes can then be detected and, if
>> necessary, extra runs can be started to update the changed graphics.
>>
>> I need the second run to create and start the ImageMagick batch script,
>> but the collected info in the *.tuc file prevents ConTeXt from starting
>> a second/third run. Currently I use a batch file that simply deletes the
>> *.tuc file and then calls 'context'. As there is no bookkeeping, all the
>> graphics are recreated then.
>>
>>
>> Peter
>> ___________________________________________________________________________________
>> 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
> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: mkiv: way to signal extra run(s)

[Aditya Mahajan]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 858 bytes --]

On Sat, 29 Sep 2012, Peter Rolf wrote:

> Am 29.09.2012 16:24, schrieb Philipp Gesang:
>> ···<date: 2012-09-29, Saturday>···<from: Peter Rolf>···
>>
>>> Hi,
>>>
>>> just wondering. Is there a official way to signal ConTeXt from a module,
>>> that an extra run is needed?
>>
>> Hi Peter, some time ago I got this answer from Hans:
>> http://www.mail-archive.com/ntg-context@ntg.nl/msg45820.html
>> (Today the table is “job.variables.tobesaved”.)
>>
> Hi Philipp,
>
> that should work. I was planing to save the graphic hash data (id-> file
> name) as lua file anyway and make use of that data in the following runs
> (compare new and old hash). Storing a checksum of that file should be
> all I need then.


Depending on what you want to do, you may be able to delegate all the book 
keeping to the filter module.

Aditya

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________