I'm thinking to develop a plugin to manually/automatically check for new version of NPP and offer the possibility of downloading them and start the install.
Is there a maintained file that one can easily check to get the latest release version?
If I can avoid it, I don't want to go the unreliable way to do html parsing.
It would be nice also to have a link to the current installer to download.
Thank you,
Franco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think you should focus to update Npp-Plugins and Npp. The problem: Most of the plugins, but not all, are on SF npp-plugins site. At the momemt the homepage of this SF has no content. Therefore we can add a file for currently available versions. Same should be done on Npp homepage.
For me it makes no sense to use a RSS feed, because it needs to be updated. A special file (PHP, javascript or whatever) for this updater makes sense. This needs also to be updated, but we know it is for the plugin. I don't know the soluton in open source project Miranda, but we should have a look on it and maybe we can use the code to improve the developing time.
Best Regards
Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How can I retrieve a list of plugin run by the user?
How can I find the current version of the plug in? Each plugin should be queried.
The plugin should also tell me the URL where to look for the latest version, as well as the URL for downloading the latest version.
How can I install the new plugin since the old one is running and and cannot shut it off?
The above would be much easyer to implement in NPP... since it know the plugin loaded.
I could push a request message through the queue, each plug in interested to be updated would have to respond to the message with the necessary information and let the original request through for other plugins to receive.
As a starting point I was thinking about NPP alone because I can get the version form the module, check it somehow online and figure a way to create the URL of the file to download and run. I can also issue a WM_CLOSE to try shutting down the current version before installing. That much I could do.
Obviously it would be much easire to have a text file lastversion.dat with the current version available online and a fixed URL for the last install file instead of a filename containing version information.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I already made a small start with something that reads the rss feed from the Notepad++ releases, currently thats the only way to retrieve the last version. Its not anywhere near usefull yet, but you can get the sourcecode if you wish (it reads the title of the first item out of the rss feed and prints that, now it displays the last release as notepad++ 4.3 source).
I dont think you can get a direct download link as sourceforge uses different mirrors depending on your location so I guess its best to adhere this behaviour, but the rss feed does give a link to the released package.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They have some php script displaying the latest version depending on the value supplied in the GET commands. The URl didnt work in Firefox but maybe its temporarily down. I guess a php file would be easier to parse, but it also has to be manually maintained, thats why I used that RSS feed, it's automated (when you uplaod a new release SourceForge alters the rss feed).
You cannot use the miranda code btw, it uses loads of internal miranda functions and services.
Switching between rss and php is not very much work I think, you jsut have to alter the parser, the rest is the same (ie getting your file using http, displaying latest version of parser results, settings and threading).
I do vote for a npp-plugins homepage, the current index listing isnt very nice.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking to develop a plugin to manually/automatically check for new version of NPP and offer the possibility of downloading them and start the install.
Is there a maintained file that one can easily check to get the latest release version?
If I can avoid it, I don't want to go the unreliable way to do html parsing.
It would be nice also to have a link to the current installer to download.
Thank you,
Franco
I think you should focus to update Npp-Plugins and Npp. The problem: Most of the plugins, but not all, are on SF npp-plugins site. At the momemt the homepage of this SF has no content. Therefore we can add a file for currently available versions. Same should be done on Npp homepage.
For me it makes no sense to use a RSS feed, because it needs to be updated. A special file (PHP, javascript or whatever) for this updater makes sense. This needs also to be updated, but we know it is for the plugin. I don't know the soluton in open source project Miranda, but we should have a look on it and maybe we can use the code to improve the developing time.
Best Regards
Jens
Here some to work with plugins:
How can I retrieve a list of plugin run by the user?
How can I find the current version of the plug in? Each plugin should be queried.
The plugin should also tell me the URL where to look for the latest version, as well as the URL for downloading the latest version.
How can I install the new plugin since the old one is running and and cannot shut it off?
The above would be much easyer to implement in NPP... since it know the plugin loaded.
I could push a request message through the queue, each plug in interested to be updated would have to respond to the message with the necessary information and let the original request through for other plugins to receive.
As a starting point I was thinking about NPP alone because I can get the version form the module, check it somehow online and figure a way to create the URL of the file to download and run. I can also issue a WM_CLOSE to try shutting down the current version before installing. That much I could do.
Obviously it would be much easire to have a text file lastversion.dat with the current version available online and a fixed URL for the last install file instead of a filename containing version information.
For plugins we can create a spezial PHP file with a table of version info, link, etc. on SF npp-plugins.
Best Regards
Jens
I already made a small start with something that reads the rss feed from the Notepad++ releases, currently thats the only way to retrieve the last version. Its not anywhere near usefull yet, but you can get the sourcecode if you wish (it reads the title of the first item out of the rss feed and prints that, now it displays the last release as notepad++ 4.3 source).
I dont think you can get a direct download link as sourceforge uses different mirrors depending on your location so I guess its best to adhere this behaviour, but the rss feed does give a link to the released package.
They have some php script displaying the latest version depending on the value supplied in the GET commands. The URl didnt work in Firefox but maybe its temporarily down. I guess a php file would be easier to parse, but it also has to be manually maintained, thats why I used that RSS feed, it's automated (when you uplaod a new release SourceForge alters the rss feed).
You cannot use the miranda code btw, it uses loads of internal miranda functions and services.
Switching between rss and php is not very much work I think, you jsut have to alter the parser, the rest is the same (ie getting your file using http, displaying latest version of parser results, settings and threading).
I do vote for a npp-plugins homepage, the current index listing isnt very nice.