New built-in Plugin Admin (Plugin Manager) is ready

guy038

Thanks, for all your clarifications :-)

Regarding my last statement, I’m so used to have, on my laptop, several versions of N++, at a time, all located in a user-defined folder, not related with any system-protected area that I had just forgotten the particular case you were talking about !

donho

@dinkumoil said:

After testing the new binaries I want to precise this statement according to my experience.

The plugin DLL file should be placed at the root level of the ZIP file. It has to be the only DLL file on this level.
The root level of the ZIP file can also contain additional files and folders which will be copied to the users harddisk as well.
Everything what gets copied from the ZIP file will be stored under <Npp-installation-folder>\plugins<plugin-name>.
Presumption: Additional DLL files needed by the plugin have to be placed in an arbitrary subfolder because the destination folder <plugin-name> gets named after the DLL file placed on the ZIP root level.

Very accurate description you made. It will be included in the PA guide line if I’m allowed to use it.

dinkumoil

@donho said:

It will be included in the PA guide line if I’m allowed to use it.

Of course, feel free to do that.

Hsilgos

Are you sure you did your last changes to both versions of GUP and Android++?
For me seems that x64 works with new scheme, but x86 works with old

dinkumoil

@Hsilgos said:

For me seems that x64 works with new scheme, but x86 works with old

I’ve tested both 32 bit and 64 bit Notepad++ and both worked with the new scheme.

donho

@Hsilgos

Are you sure you did your last changes to both versions of GUP and Android++?
For me seems that x64 works with new scheme, but x86 works with old

Because you use Android++ instead of Notepad++.

Hsilgos

@donho Yes, Notepad++ for sure =D
The rest of message should be correct

donho

@dinkumoil Sorry, I didn’t read your description attentively. The correct info about packaging is following:

The plugin DLL file should be placed at the root level of the ZIP file.
The root level of the ZIP file can also contain additional files (DLL files or data files needed by the plugin) and folders which will be copied to the users harddisk as well.
Everything what gets copied from the ZIP file will be stored under <Npp-installation-folder>\plugins<plugin-name>.

The other DLLs can be at the root level with plugins DLL because Notepad++ will load only the dll has the same name as its containing folder. The other DLLs are just ignored.

chcg

Having a hash of the main plugin dll might be still of interest, if you want to provide a “safe” mode with just starting plugin dlls with correct sha-256 hash.

pnedev

@donho ,

I just noticed that when testing the NppGTags x86 plugin installation it was put in C:\Users\me\AppData\Local\Notepad++\plugins\NppGTags instead of C:\Program Files (x86)\Notepad++\plugins\NppGTags. It is working fine but I didn’t get the impression that it would be installed there.
Is that the intended behavior?

dinkumoil

@pnedev said:

it was put in C:\Users\me\AppData\Local\Notepad++\plugins\NppGTags instead of C:\Program Files (x86)\Notepad++\plugins\NppGTags

I did my previous test with portable installations of NPP, with a local installation I can confirm this behaviour. My plugins partially fail to work correctly, they don’t find their own DLL (required for extracting version information for the About box) and their documentation file anymore.

The current behaviour is caused by the fact that it was intentional to provide a method of plugin installation which requires no restart of Npp. Thus the plugin installer can’t copy the plugin files to the installation folder of Npp because usually this is a protected location and would require admin rights to do so.

Since we already discovered that there is a high risc that a restart-free plugin installation will cause problems with certain plugins (NppFTP seems to be one of these) @donho stated here that this behaviour will be changed. Thus in the future the installation folder should be <Npp-installation folder>\plugins\<plugin-name> again.

donho

@pnedev

Is that the intended behavior?

Yes, I confirm it.
From now on all plugins will be placed in its folder which has the same name, so that any data or dll that plugin needs can be placed arbitrarily in this folder.

I invite you to check the guide for being included in plugins list, it’ll be updated as soon as there’s any change of specs.

donho

@dinkumoil

@donho stated here that this behaviour will be changed. Thus in the future the installation folder should be <Npp-installation folder>\plugins<plugin-name> again.

Not sure about the point you’re talking about. Could you elaborate it?

dinkumoil

@donho said:

@dinkumoil
Not sure about the point you’re talking about. Could you elaborate it?

In this comment I stated:

2.After plugin installation Notepad++ is not restarted. That seems to be nice at first glance but causes serious problems.

Your answer in this comment was:

The 2nd point you mentioned is a bug, will be fixed in the future.

I interpreted this in that sense that in the future after plugin installation Npp will be restarted again to avoid problems with plugins which need this behaviour. We have seen that sending a NPPM_READY message to plugins after installation is not sufficient because @chcg reported in this comment that NppFTP still isn’t initialized correctly:

@chcg said

For NppFTP the NPPN_READY doesn’t solve it completely. Now the docking and the message window are constructed/ visible, but the content is still not there. Maybe there is another difference to the start of n++ itself.

The thing @pnedev and I wanted to point out is that with a local installation (performed by installer exe) the plugins currently are not installed under C:\Program Files\Notepad++\plugins but under C:\Users\<user-name>\AppData\Local\Notepad++\plugins. This difference causes problems since it is only possible to query the installation folder of Npp but not the storage location of the plugin itself.

My current algorithm to get the storage location of my plugin DLL file and its documentation file is as follows (if this algorithm is wrong please point me to the correct method to do that):

Send NPPM_GETNPPDIRECTORY to Npp to query the installation folder of Npp.
Append plugins.
Append the plugin name.

This would result in e.g. C:\Program Files\Notepad++\plugins\AutoCodepage. But currently there is no folder of this path since the plugin gets installed under C:\Users\<user-name>\AppData\Local\Notepad++\plugins\AutoCodepage.

donho

@dinkumoil

The thing @pnedev and I wanted to point out is that with a local installation (performed by installer exe) the plugins currently are not installed under C:\Program Files\Notepad++\plugins but under C:\Users<user-name>\AppData\Local\Notepad++\plugins.

Damn! I miss again!
https://pbs.twimg.com/media/ChxfvQVVEAEQvXH.jpg

I interpreted this in that sense that in the future after plugin installation Npp will be restarted again to avoid problems with plugins which need this behaviour.

No, it’s not what I wanna do. I have added NPPN_READY, obviously it’s not enough, there is (are) other notification(s) missing we just need to add it (them).

dinkumoil

@donho said:

No, it’s not what I wanna do. I have added NPPN_READY, obviously it’s not enough, there is (are) other notification(s) missing we just need to add it (them).

Why do you want to make life difficult for you (and plugin developers which have to assist you to find the required notifications)? When plugins get updated or uninstalled a restart of Npp happens (currently) anyway.

Revert the installation path for portable and local Npp installations to the same location and restart Npp to perform actual plugin installation in admin mode - you (and we plugin authors) would be ready. That’s also KISS.

chcg

Some points from PluginManager feature requests:

https://github.com/bruderstein/nppPluginManager/issues/33
Feature Request: UDL repository -> update not just plugins, but also UDLs and maybe themes
https://github.com/bruderstein/nppPluginManager/issues/119
Disable Plugin updates -> meaning no automatic check for updates + specific right on user\plugin base
https://github.com/bruderstein/nppPluginManager/issues/133
Import/export installed plugins -> restore/sync current plugin constellation on a different computer/with a different user
https://github.com/bruderstein/nppPluginManager/issues/42
Find dead links -> Create a script to check if the provided list is still consistent and all plugins\links from the list still exist

pnedev

@donho ,

I second what @dinkumoil said:

The installation path for plugins should be $Notepad++_Install_folder\plugins mainly because of the portable version of Notepad++.

If you decide to keep the installation destination as it is now (C:\Users<user-name>\AppData\Local\Notepad++\plugins) then perhaps the user should be asked if the plugin is to be installed only for him/her or for anyone using the computer.

@dinkumoil ,

The Notepad++ restart upon plugin installation is not very elegant since this is just a DLL being plugged into the editor and all it needs to work properly is the right sequence of notifications. Now, I don’t address here the permissions problem to install the plugin in a place needing an elevated rights - I’m not quite aware of that issue at the moment.

If you need to get the real plugin DLL installation path here is what I do:

TCHAR gDllPath[MAX_PATH];

BOOL APIENTRY DllMain(HINSTANCE hModule, DWORD reasonForCall, LPVOID )
{
switch (reasonForCall)
{
case DLL_PROCESS_ATTACH:
::GetModuleFileName((HMODULE)hModule, gDllPath, MAX_PATH);

Don,

AFAIK, what a plugin needs to initialize properly is loading its main DLL (LoadLibrary() - this will also trigger DLL_PROCESS_ATTACH) then call getName() and getFuncsArray() and setInfo() and last send NPPN_READY notification. That should make it fully functional (unless I’m missing something).

In the case of updating a plugin, the plugin has to properly unregister itself with Notepad++ on DLL_PROCESS_DETACH so there are no conflicts in the consequent plugin reload.

donho

@pnedev

The installation path for plugins should be $Notepad++_Install_folder\plugins mainly because of the portable version of Notepad++.

If Notepad++ is not installed in “Program Files” and doLocalConf.xml is present, Plugins Admin will install plugins into “$Notepad++_Install_folder\plugins” - is it not the case for you?

Edit: I just checked in current official released packages, GUP.exe, which is needed by Plugins Admin, is not available in any zip packages (and it should not be, since GUP.exe will get installer EXE and execute it - that’s not the expected behaviour of portable version). I have no (yet) a perfect solution for it. So both GUP.exe and nppPluginList.dll will only be included in installer in the next release.

The Notepad++ restart upon plugin installation is not very elegant since this is just a DLL being plugged into the editor and all it needs to work properly is the right sequence of notifications.

I couldn’t agree more.

AFAIK, what a plugin needs to initialize properly is loading its main DLL (LoadLibrary() - this will also trigger DLL_PROCESS_ATTACH) then call getName() and getFuncsArray() and setInfo() and last send NPPN_READY notification. That should make it fully functional (unless I’m missing something).
In the case of updating a plugin, the plugin has to properly unregister itself with Notepad++ on DLL_PROCESS_DETACH so there are no conflicts in the consequent plugin reload.

Yes, that’s my point. The process to load a just installed plugin is the same as the one which is loaded from the startup of Notepad++.
Is there any other plugin doesn’t work after its installation by Plugins Admin?

dinkumoil

@pnedev
Thank you for your code snippet. I had this method not in mind because in Delphi the DLL entry function is hidden in the RTL. It is only possible to install a hook function with the following signature DllMain(DWORD reasonForCall). The DLL instance handle has to be obtained from a global variable called HInstance.

@pnedev said:

The Notepad++ restart upon plugin installation is not very elegant since this is just a DLL being plugged into the editor and all it needs to work properly is the right sequence of notifications.

what a plugin needs to initialize properly is loading its main DLL (LoadLibrary() - this will also trigger DLL_PROCESS_ATTACH) then call getName() and getFuncsArray() and setInfo() and last send NPPN_READY notification.

Yes, this should do the thing but NppFTP seems to be an example where this sequence isn’t sufficient. Maybe there are other plugins where it is the same (Wild guessing: There could be required some WM_XXX messages, in the worst case this may be plugin dependent).

My point is the following:

Plugin installation happens only one times, also uninstallation. In contrast updating a plugin happens more frequently.
Performing plugin updates restart-free is (as far as I know) a complicated thing, at all it makes no sense (see below).
If it is not possible to update plugins restart-free why there should be invested effort to make installations restart-free?

Why do I think restart-free plugin updates are complicated?

Plugins can manipulate the UI of Npp in various ways:

Inserting icons into the toolbar.
Inserting icons into menus (Menu Icons plugin).
Manipulating the whole toolbar (Customize Toolbar plugin).
Adding an entry to the Plugins menu including a submenu.
Adding other menu entries in arbitrary menus of Npp (ToolBucket plugin) or even adding a new menu in the menu bar (TextFX plugin).
Opening (docked) windows and modeless dialogs.
Inserting new windows in Npp’s UI (e.g. HEX editor’s address bar above the hex data).

All these manipulations have to be reverted when updating a plugin before Npp unloads its DLL and this case should be distinguishable from simply terminating Npp, thus it can’t be done in DllMain as a reaction to a DLL_PROCESS_DETACH call - there has to be a new Npp notification to inform plugins that they are about to be uninstalled (updating is a sequence of uninstall - install).

Furthermore, currently there is only a NPPM_ADDTOOLBARICON and no NPPM_REMOVETOOLBARICON (see 1.); there is only a method to add entries to the plugin’s submenu in the Plugins menu and no method to remove them (see 4.); the other points (2., 3., 5., 6. and 7.) are based solely on plugin code and require more or less effort to revert them.

Why do I think restart-free plugin updates make no sense?

There are two categories of plugins:

Stateless plugins
Stateful plugins

Stateless plugins perform simple actions, e.g. my AutoCodepage plugin (it monitors user actions and switches the document encoding scheme if neccessary) or @donho 's PorkToSausage (works only on-demand). These plugins are not critical for restart-free plugin updates.

Stateful plugins create a state by themself, e.g. NppFTP, @pnedev 's Compare plugin, scripting plugins with debugging capabilities (e.g. CS-Script) or the HEX editor plugin. These plugins are critical for restart-free plugin updates.

A state includes:

open windows (all plugins mentioned above)
open network connections (NppFTP)
set path for FTP session (NppFTP)
processing data and displaying results (Compare)
state of a debug session (CS-Script)
maybe more that I’m not aware of at the moment

To restore this state after a plugin update requires much effort, I guess that nobody wants to do that, maybe its even impossible. Thus restart-free updating makes no sense - after updating users would have to restore the desired state by themself, there would be no benefit compared to the current situation.