Custom tools and GUIDs?

[Kimon]

Hi!

I have another suggestion to make concerning custom tools. So far the only way to call a custom tool from a batch is to call PDFTools with the tool's ID (apparently a GUID). Why not call it https://speedtest.vet/ https://vidmate.bid/ by its name like any standard tool. All it takes is for users to give their custom tools a unique name and unicity could easily be checked by the program when a custom tool is created.

Apart from providing a more homogeneous way of calling tools, this would have several advantages: (1) the registry wouldn't get even more bloated than it is already; and (2) this would make a future portable version of PDF-Tools possible.

Indeed having a portable version of PDF-Tools would be a great improvement for obvious reasons. I hope this will happen some day...


Thanks

[TrackerSupp-Daniel]

Hi, Kimon

It may be possible to use unique names instead of a GUID, however these would still need to be added into the registry, thus there would be no impact on "registry bloat". I will mention the Idea to our dev team and see what they think.
Following that, we have no plans to offer a portable version of PDF-Tools for the forseeable future. Unlike the editor which for the most part requires someone to be directly attending the machine, PDF-Tools is highly automatable, leading to many possible issues/dangers with portable devices.
Our current licensing scheme also does not allow for portable versions of any sold products other than the Editor.

Kind regards,