A script to create a setup for each plugin

[ctiberg]

Yeah, that's much better, I think.. My opinion about the other look of NSIS isn't solely personal prejudice - conforming to the 'standard' makes users feel at home, and that's one of the most important things of an installer, IMHO - confuse or scare the user, and he might abort, and never see the rest of your great product...

[Ergo]

New version of SynPlus 2.0 beta 3 now comes with installer Very convenient! I am not a newbie in Total Commander's affairs and know much about plugins but even I found it extremely convenient to install plugins through installer...

Little wish. When I was installing this plugin was already in use so I got an error because its files were blocked. It would be nice to perform Total Commander's cm_UnloadPlugins command before copying files. Is it possible?

[icfu]

Installer doesn't accept variables!

I use variable %TC_PLUGINS% which is defined as "D:\Profile\Icfu\Anwendungsdaten\Total Commander\Plugins" here to make my life easier.

Furthermore:
There is no chance to look inside the archive before installing (for example extracting the readme) and therefore no chance to manually install the plugin.

Without control I'm feeling like a guinea pig and that's why I have to admit that I don't like the current installer at all.

Icfu

[djk]

2icfu
I fully agree with you. I've also put my opinion here before.
I understand idea of making life easier for some less experienced users (or more lazy ) but I still prefer to install the plugins manually.
I really don't like the new way of plugin's distribution (as setups).
I hope Fabio will create a new version of tcplugin with "Unpack only" option.

[fabiochelly]

2icfu
What is this variable %TC_PLUGINS%?
Where is it defined?
And it's very easy to add a readme file at the beginning of the setup. But I will propose it in my program to automatically display it in the installer.

It would be nice to perform Total Commander's cm_UnloadPlugins command before copying files. Is it possible?

Does any one know how I can do that from an external program?

[Lefteous]

2fabiochelly

What is this variable %TC_PLUGINS%?
Where is it defined?

It's an environment variable, that has been defined user- or systemwide. You should always expand a given path using ExpandEnvironmentStrings

[icfu]

What is this variable %TC_PLUGINS%?
Where is it defined?

You can define environment variables under Control Panel-System Tab-Advanced-Environment settings (I hope that is correct, german XP version here...) or directly in key HKEY_CURRENT_USER\Environment.

And it's very easy to add a readme file at the beginning of the setup.

Although that's a very good idea of course, readme was just an example, I just don't like the idea in general that I can't open the setup archive for further examination like I am able to do with a self-extracting zip for example.

Well, regarding your answer I I think that NSIS doesn't offer such possibilities then? I can only hope that all plugin authors will offer two versions from their plugins in the future so users have the choice what to use.

@Lefteous:
Thanks for link to msdn, seems that the author of AmpView could need that one, too...

Icfu

[fabiochelly]

A new version is out.
- the plugin creator can now add a readme file to the setup
- The user can uncheck a checkbox to unpack files only
- The setup checks the environment variable TC_PLUGIN

You can download it here:
http://totalcommander.free.fr/fabio/tcplugin.exe

Here is a screenshot of the program:
Image: http://www.chelly.net/disk/tcplugin.png

[icfu]

The user can uncheck a checkbox to unpack files only

That's great, thx.

The setup checks the environment variable TC_PLUGIN

What do you mean by "checking"?
Do I have to create a variable "TC_PLUGIN" instead of "TC_PLUGINS" now and script will read that variable and propose the correct path value?

I think that's a misunderstanding here, either on my or on your side regarding variables, not sure...

Icfu

[fabiochelly]

I don't understand.
If you have a envVar TC_PLUGINS defined on your system, the setup will autiomatically propose %TC_PLUGINS%\PLuginName as default path.
Isn't it what you were asking for?

[icfu]

Nope, that was a misunderstanding. The installer doesn't allow variables to be manually entered in path name in general, that's all I wanted to explain.

That means if I manually try to change path to something like %UserDefinedVariable%\WLX\PluginName the install button is grayed out!

If you now created a workaround, looking for variable %TC_PLUGINS% automatically and expanding it without me having to enter the path name, it helps me, sure.
But it won't help other users with other environment variables at all.

I don't know NSIS, maybe it's not your fault but a limitation of the installer that simply doesn't allow path names with variables? Maybe someone else can answer that question.

Anyway, thanks for your efforts, I'll check the next available plugin using your script if it works like I am expecting now.

Icfu

[djk]

2fabiochelly
Thanks for the new version.

[Hacker]

fabiochelly,

Does any one know how I can do that from an external program?

From http://ghisler.ch/board/viewtopic.php?p=6890 :

I send all internal commands to TC window via WM_USER+51 message.

and from http://ghisler.ch/board/viewtopic.php?p=3808 :

The command cm_UnloadPlugins will unload all plugins. You can send TC the following command:

wm_InvokeMenuCommand=WM_USER+51

with WPARAM set to the command you want to pass to TC.

HTH
Roman

[LonerD]

Links are die.
Anybody can load this script and Plugin Setup Creator too?

[dott]

What's wrong with Plugin auto-install HOWTO