Hi all,

since we gained the safety framework which requests explicit consent for
running external scripts it's now time to release the real beast :)

I propose to introduce new inset layout parameter (say TriggerScript) which
will would execute user-defined script/binary processing the content of the
inset.
Something similar to knitr or gnuplot extensions but much easier for user to
directly declare in inset layout definition.

Inset ID, sequential number of export process and target (latex/html) would be
provided to the external script (ie providing position with respect to other
processed insets and detecting each new export process) so it can do more
powerful magic in backgrounds.

Before I start playing with coding how big is the opposition to such feature,
I am well aware that it more widely opens doors to various catastrophes 
triggered
by 3rd party scripts... ?

Pavel

Reply via email to