Plugin auto-install HOWTO (TC 6.5 or newer)

[Alextp]

Add to 1 post inf about 'lng': to what folder it should install, 'prg':it is missed there

[ghisler(Author)]

No, there is a separate type "lng" which should be used for language files! Language-specific hlp and chm files can also be installed there.

[Alextp]

You didnt get it. There's type 'prg' which you didn't mention in 1 post. //it used now in russian language pack.

[ghisler(Author)]

Ah, I see - normally prg shouldn't be used because it doesn't work with U3 USB sticks (that's why there is a separate U3 installer for the Russian language pack). I have documented it now anyway for users who need it.

[Alextp]

sugg.: file2/type2 field. For installing wcx+wlx. wfx+wdx.

[sqa_wizard]

I recently used the type=prg to install 32-bit dlls required for sftp plugin into TC folder.
It works fine so far

To install the x64 files too, they have to be installed into subdirectory "64".
My first guess: No problem, just specify a defaultdir like it is used for plugins (wcx, wdx,wfx, wlx)

Code: Select all

type=prg
file=libssh2.dll
defaultdir=64

Bad cards ... it is just ignored for prg

Any chance to get support for this too?

[Flint]

sqa_wizard
Just put the files into subdirectory 64 inside archive.

[sqa_wizard]

Thank you Flint!
I put the files into subdirectory "64" inside archive and used

Code: Select all

type=prg
file=64

...that did the trick

[kotlomoy]

I just realized that my plugin doesn't create directory when autoinstalling. This is pluginst.inf:

Code: Select all

[plugininstall]
description=BranchViewExtended 1.03: Branch view with subfolder sizes (http://www.ghisler.ch/board/viewtopic.php?t=24238)
type=wfx
file=BranchViewEx.wfx
defaultdir=BranchViewEx

Plugin is installed to %COMMANDER_PATH%\wfx\ instead of %COMMANDER_PATH%\wfx\BranchViewEx\. What is wrong?

[MVV]

kotlomoy,
It suggests correct path for me, %COMMANDER_PATH%\Plugins\FileSystem\BranchViewEx\ (I install WFX under FileSystem subdir). But it seems that TC searches for *.WFX files in order to determine WFX subdir path because when I put a WFX into FileSystem dir, TC suggested %COMMANDER_PATH%\plugins\BranchViewEx as plugin destination path. Please note that plugin dir is appended to path in both cases so it is probably something strange in your special case. Maybe some INI settings or installed files caused this.

[ghisler(Author)]

Maybe you had a previous installation of the plugin in %COMMANDER_PATH%\wfx\? TC will always offer to overwrite an already installed plugin with the same name.

[Mikefield]

The type field contains the plugin type: wcx, wfx, wlx or wdx (new plugin type for file content data), lng for additional languages, or prg for the Total Commander directory.

How do you think about a type "util" for TC utilities like TCMatch? This would be located in %Commander_Path%\Plugins\Util


mf

[MVV]

Mikefield,
You can't move tcmatch.dll from TC dir to a subdir so prg type should be used for it. Regarding other tools, different users put them into completely different places...

[Mikefield]

Mikefield,
You can't move tcmatch.dll from TC dir to a subdir

That's not correct. Tcmatch is moved to a subdir in my configuration. In wincmd.ini is a TCMatch= parameter.
So back to "util" subdir. What about a "UtilDir=" in wincmd.ini [Configuration]? Then it makes sense to add an "util" type.


mf

[MVV]

Ah, there is an INI option for this library...

I don't think that such third-party tools really need TC installation mechanism.