* Run Plugins via Expressions

[tatewise]

This is an advanced power user feature, but has potentially far reaching benefits if used wisely.

Currently, Plugins can only be run via the Tools menu somewhat disjointed from all other FH program features.

Within Plugins any FH Function can be invoked via fhCallBuiltInFunction().

This requests a complementary capability whereby an FH Function can invoke a Plugin script.
Let us assume such a function would be =CallPlugin() where the first parameter is the Plugin Name followed by parameters to pass to the Plugin, and parameters can be returned.

I am thinking that perhaps the Plugin Filename, Title, and main Function must all have the same Plugin Name as used by the =CallPlugin() function. The Function in the Plugin would have parameters to match the =CallPlugin() parameters. Values returned by the Function in the Plugin would be returned via the =CallPlugin() function.

Alternatively, the =CallPlugin() function would simply run the Plugin with the matching Plugin Name. In the Plugin API there would be two functions fhGetParameters() and fhSetParameters() to receive and return parameter values.

With this new feature, anywhere Expressions with Functions are allowed, Plugins can be invoked. So operations that cannot be performed by FH Functions and Data Refs could be performed by a Plugin. This could apply to Record Window Columns, Narrative Sentence Templates, Queries, Reports, Diagrams, etc. One significant caveat is that if the Plugin performs an in depth database search, especially with a large database, then using the features listed above may become (very) sluggish.

[tatewise]

Wish List Ref 547 Run Plugins via Expressions has been created.