Dark One wrote:recomendation: add a new field: readme=myreadme.txt and a button on your new dialog which will allow users to see plugin's readme file. perhaps also readmedeu=myreadme.de readmerus=myreadme.ru or a combo box like in Kconfigure. allow html files along with txt...
Yes, I also think it would be a good solution. Not only to read what the plugin is for but what's more important to read its requirements. In some cases you need to do something before installing it, eg. download and install some additional libraries (eg. MATLAB plugin). If you don't do it you get errors during installation.
In some cases using a plugin can a be a bit complex so it would also be nice to be able to read the instructions how to use it. Of course one can go to plugin folder and then read it manually but why not to make it easier?
Adding version would be also nice cause now it's usually added by authors to description field, but if there are several descriptions (I mean for different languages) he has to copy the version number several times instead of putting it only once.
I hope that the plugin-self-installation system will be expanded in future versions.
Reason: http://www.totalcmd.net/plugring/EventLog.html
great Plugin which is one part FS and the other part Lister
Or is there any way to write a pluginst.inf that will install
both files from one zipfile ?
Christian,
You've never put your opinion on these suggestions. As there are more and more plugins (over 450) and many of them need user actions before they can work properly (or even before installation) I think it would be a good solution to add suggested above field. What do you think about?
Is it possible to remove outdated files during a plugin auto-install procedure?
I wants to remove olf fileversions, the newer files have a different name.
For example:
tc-apis-1.5.jar must be removed
and tc-apis-1.6.jar should be installed
Is this possible or should i remove it in my plugin code?
Currently there is no way to remove files. What you can do is place a 0 byte file with that name in your archive. This way, the old file will be overwritten with a 0 byte file, saving the disk space of the old file. Another alternative would be to delete the old file from within your plugin when it is used for the first time. You may also combine the two, and delete the old file only when it is 0 bytes long.
ghisler(Author) wrote:Currently there is no way to remove files. What you can do is place a 0 byte file with that name in your archive. This way, the old file will be overwritten with a 0 byte file, saving the disk space of the old file. Another alternative would be to delete the old file from within your plugin when it is used for the first time. You may also combine the two, and delete the old file only when it is 0 bytes long.
But why change the name anyway?
But it will still take one cluster and some screen space, when the folder is being browsed. Not a big deal, but not a nice solution.
Sorry, my mistake. It will still some space in files table.
The only better solution I see is writing a helper plugin that will manually do the instalation.