Bo, the 1.3.x external inset doesn't give you any eye candy but it will enable you to do all that your require. The 1.4.x version will give you the eye candy too.
I realized the 'virus' problem after I sent the email. But I was thinking something like 'manual activation' ...
Menaing I'll have to click "yes" for each of several hundred
code snippets implemented with a "cat sourcefile" inset
each time I print? Nope.
Anyway, security will be a hard-to-overcome problem.
It is much easier with external insets for specific applications. Then you know the code won't run anything but the intended app, unless the app itself is vulnerable somehow.
If you need something unusual, just make an external inset for my_shellscript which do what you want.
I am curious about how external inset can handle 'all that I require'. For example, there is a program called csv2latex which can turn a csv formated table into latex code. How exactly can I insert a csv2latex generated (dynamic) table with external inset?
You write an external inset for csv2latex. Then you have dynamic tables that will update whenever the csv file is altered (for example by exporting from some spreadsheet or database)
Helge Hafting
