asPluginManager

[Tadjio]

I suggest that asPluginManager offers a second checkbox for this functionality:
1. checkbox to "uninstall" theplugin by renaming the folder
2. checkbox to hide the plugin from view

That makes sense!

[andreas]

Hi,

very good idea. But I missed the idea behind it. Why do you want to hide a plugin which is perhaps enabled?

I understand:

Uninstalling/Renaming (check if its buggy)
Disabling (check the changes quickly)

But I do not understand:

Hiding

Only to save space in the next ASP run? You can click on the triangle in the UI header to archive this in the current ASP run.

Andreas

[nyukuri]

maybe personally I won't use a certain plugin, but others may use it and share presets or even images with xmp file with me. To see their images correctly and to see the result of presets correctly it is good to have the plugin - hidden from my view and use, but still in "silent mode" effective ...
also this will help not loosing the info in an xmp file of in image just because a plugin is not installed, a problem that was discussed in this thread earlier

[andreas]

Hi,

the new asPluginManager is available on the Corel plugins site. It has support for enabled/disabled diplay for supporting plugins. See here: http://forum.corel.com/EN/viewtopic.php?f=96&t=47074

Andreas

[andreas]

Just updated the package because of an endless "new version available dialog"

Andreas

[andreas]

Hi,

new version 1.0.5 on Corel plugin page

- Automatic update version check for all plugins listed on the Corel site (30min turnaround)
- Other plugin devs may send me a pm or mail with their current download link to integrate in the database

Andreas

[nyukuri]

Thank you Andreas, that's an excellent update and works fine, I discovered that my plugins are not as up-to-date as I thought...
I'll donate a little something for your great work and hope that others will do the same! I hope Corel will include asPluginManager and asGPS soon as standard tools in a new version of ASP as they did with other plugins before

Just a few thoughts for improvement:
- the green version numbers are a bit hard to read on the gray background, maybe a darker green would do
- "no tooldata" makes people wonder or even scare them that their plugin has a problem... maybe that field is better left empty when there is no tooldata. Or you provide some explanatory information on its meaning when clicking on that field

[andreas]

Thanks for the feedback, I updated the green, made all checked versions bold and added tooltips for ToolData etc. Will be available in the next update.

Andreas

[patrickh]

thanks for the update

[Tadjio]

I have just downloaded version 1.0.6 and it's great just to be able to check that all my plugins are up-to-date
I found 4 that weren't and immediately updated them. Thanks.

I have lost the plot - will we be ale to stop plugins appearing in the Tools Panel without disabling them?
That would reduce the clutter considerably

[andreas]

Its on my list.

The workaround will be as follows:

user wants to hide a plugin:
If the plugin is loaded and visible, asPM copies the Info.afpxml file to a backup name, creates a new one without the ui files in the ui file list.

user wants to unhide it again.
To reenable, asPM copies the original Info.afpxml file back.

Every update of the plugin will reenable its view. You can disable the ui again after plugin update even before restarting ASP.

Thats the plan.

Andreas

[Tadjio]

I have bought you a couple of beers (as advance payment:-)

[nyukuri]

Thank you for the quick update! The green version numbers are now well readable. But the quick info should be shorter and maybe rephrased:

1. "This plugin does not support additional info for asPluginManager. If it would, it would be possible to show its" ... and here the text is cut on my Win7 system!
Let it maybe just say: "this plugin does not fully support asPluginManager"
("not fully" because update info can be available and some "support" is therefore there)

2. "there is no version info available for this plugin"
no VERSION info? but I DO see a version number...!
It should maybe read: "no update info available"

3. "This plugin is installed in its newest version"
should read simply: "plugin is up-to-date" or "latest version installed"

PS: I am looking forward to the hide/enable function...

[andreas]

Hi,

Update to version 1.0.8 on the plugin site and auto update if already installed:

Changes:

- internal redesign
- better texts, not fully ready - working on them
- support for enable/disable plugins in asPM - even for multi enable buttons like in Wavelet Sharpen.

To use enable/disable the plugins they must support the ToolData. Some are already on their way to you!

Before releasing anything which hides plugins I will have to do very intensive tests on that topic. Its possible that my "solution" will crash with several plugs.

Andreas

[nyukuri]

thank you!

In your screen shot Wavelet Sharpen seems to support already asPluginManager, not so on my system. I guess this is just an image to show what asPluginManager will be able to do once it is supported by a plugin?