Python Scripting

[nsp]

The topic wasn't about automation but scripting support for plugins.

I missed this point reading the only response from M.Ghisler.
By the way anyone is free to implement a plug-in wrapper using native interface for any interpreted language.

[billiebub]

The real power will stem from naively supporting plugin development using a well known interpreted language built right into TC. I honestly don't see it such a big task to include in TC. Developers will simply implement the required methods just like in Delphi and should all be good.

The true power here is to use an already well known language rather than reinventing the wheel. Languages such as Python, Ruby, etc are very robust and sworn by and do provide methods to integrate into other applications.

One would argue why not just write a plugin wrapper around an interpreted language? For one, you need to have all 4 plugin interfaces implemented (Lister, Content, Compression, and File System) to take advantage of all of plugin architectures. For two, you will need to add 4 instances of the plugin (if all interfaces are implemented in one plugin) to TC to load 4 instances of the plugin (scary). For three, most plugins lose ongoing development and maintenance not to forget updates to TC will render many plugins useless and unstable over time. This feature should really be part of TC to have it evolve as part of its nicely-written architecture.

[antoineL]

The real power will stem from naively supporting plugin development using a well known interpreted language built right into TC.

I should be missing something obvious, but I know of a difference between interpreted whatever (like you are proposing, even if it is in Python) and compiled whatever (like the existing plugins, even if written in Delphi ), and that difference is speed.

[billiebub]

It would be so amazing to be able to quickly write a few lines of Python code to make use of TC plugin architecture. My god the uses are infinite.

Why can't I write a quick CSV parser for a specific task and render that in a content plugin?

Why can't I write a quick pcap parser and show the source and destination IP addresses in a content plugin?

We need to sign a petition of some sort to see how many people would see a benefit to be able to "script" plugins?