Ability to Create Tools from Multiple User-Defined Tools

This Forum is for the use of End Users requiring help and assistance for Tracker Software's PDF-Tools.

Moderators: TrackerSupp-Daniel, Tracker Support, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Tracker Supp-Stefan

Post Reply
User avatar
Zardoz2293
User
Posts: 14
Joined: Thu Feb 20, 2014 11:16 am

Ability to Create Tools from Multiple User-Defined Tools

Post by Zardoz2293 »

Ability to Create Tools from Multiple User-Defined Tools. Currently, if you have 10 user defined tools and need to execute all ten you must do so individually. There needs to be an ability where you can add your the user defined (as you configured, modified tools).

Why? This way I can maintain N-number different tools that are used and run a group of them while having to maintain only the original N-number of tools and can share their functionality with other grouped batched tools without having the maintenance nightmare that currently exists. (shared functionality).

Example:
(A) "ud1 Properties"
(B) "ud2 PDF/A"
(C) "ud3 Options"
(D) "udg4 Properties + PDF/A" [composed of (A) and (B)]
(E) "udg5 Properties + Options" [composed of (A) and (C)]

If (A) was modified, both (D) and (E) would not need to be modified as they would execute (A). Under the current design if you had the functionality above you would have to modify 3 of the user defined tool scripts rather than 1.
User avatar
Tracker Supp-Stefan
Site Admin
Posts: 17824
Joined: Mon Jan 12, 2009 8:07 am
Location: London
Contact:

Re: Ability to Create Tools from Multiple User-Defined Tools

Post by Tracker Supp-Stefan »

Hello Zardoz2293,

Most if not all of the tools would require input and then output. If you need the output of one tool to be processed by the other -the current set up won't really affect the workload. And if you want to "merge" the tools so that the operations of two tools (e.g. one adds watermarks, the other some page numbering) - then there would be a conflict of some duplicating operations. Also there will have to be some complicated logic of how to treat those tools when merging that would be prone to errors.
So if you need a new custom merged tool - it is most prudent to create that separately as an 11th one and just call that combined one when needed.

Kind regards,
Stefan
Post Reply