keep plugin version independent of program version

[ksharindam]

Plugin versions should be independent of the program version.
So in some plugins (deskew, invert, bimodal_adaptive) the plugin version should be changed from 4.x.x to 1.0 or 1.1 etc.
To indicate if the installed photoquick supports the plugins build, add plugin api version in the name of the package.

Plugin api version is in plugin.h file, the line
#define Plugin_iid "photoquick.Plugin/1.0"
here 1.0 is the api version.
If something is change in the api, version will be changed to 1.1 and so on.

[zvezdochiot]

@ksharindam say

#define Plugin_iid "photoquick.Plugin/1.0"

Interesting feature.

But there is bad luck. There is no longer a separate plugin, but a whole collection. And the version for the collection is the easiest to take from the program.

[ksharindam]

Interesting feature.

This is feature of Qt, if plugin iid does not match it does not load the plugin.
If plugin of different api uses same iid, plugin loads and crashes. So plugin api version indicates compatiblity
with the program.

But there is bad luck. There is no longer a separate plugin, but a whole collection. And the version for the collection is the easiest to take from the program.

Use a version for the whole package. Plugins are independently maintained, so why take version from program. Use its own version.
And increment the vesion with each change. Suppose current version is 2.4.0, if two plugins are added, version will be 2.6
So users can have idea of how much changes have been done.

[ksharindam]

That means you have three versions.

1. version of each plugin (indicates how many times a plugin has been updated)
2. version of whole package (indicates how much progress has been done to whole repo)
3. api version of the prebuilt release. (if the plugin you built is compatible with user's photoquick)