Plugin:PackUpdater/en - Revision history

FuzzyBot: Updating to match new version of source page

2017-12-31T11:11:35Z

Updating to match new version of source page

← Older revision		Revision as of 14:11, 31 December 2017
Line 6:		Line 6:
	You can find sample configuration files [https://github.com/miranda-ng/miranda-ng/tree/master/plugins/PackUpdater/Docs/Templates here].		You can find sample configuration files [https://github.com/miranda-ng/miranda-ng/tree/master/plugins/PackUpdater/Docs/Templates here].

	# Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.		# Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g., descriptions of update components) to your <tt>langpack_*.txt</tt>.
	#; Variables in <tt>Autoexec_PackUpdater.ini</tt>		#; Variables in <tt>Autoexec_PackUpdater.ini</tt>
	#* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in {{Menu\|Events\|Pack updates}}.		#* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in {{Menu\|Events\|Pack updates}}.

FuzzyBot: Updating to match new version of source page

2017-12-31T11:08:09Z

Updating to match new version of source page

← Older revision		Revision as of 14:08, 31 December 2017
Line 1:		Line 1:
	{{PluginCard}}		<languages/>{{PluginCard}}
	Simple updater for Miranda NG premodified packs. Plugin may be interesting for pack authors who want to automate the process of updating of their packs.		Simple updater for Miranda NG premodified packs. Plugin may be interesting for pack authors who want to automate the process of updating of their packs.

			== Usage ==

	~~== Usage ==~~
	You can find sample configuration files [https://github.com/miranda-ng/miranda-ng/tree/master/plugins/PackUpdater/Docs/Templates here].		You can find sample configuration files [https://github.com/miranda-ng/miranda-ng/tree/master/plugins/PackUpdater/Docs/Templates here].

Line 35:		Line 35:

	== How it works ==		== How it works ==

	Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.		Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.

	First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:		First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:
	* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.		* in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.
	* b) in normal mode plugin shows the message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.		* in normal mode plugin shows the message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.

	{{PluginGroups}}		{{PluginGroups}}

Dart Raiden at 21:41, 6 August 2017

2017-08-06T21:41:19Z

← Older revision		Revision as of 00:41, 7 August 2017
Line 4:		Line 4:

	== Usage ==		== Usage ==
	You can find sample configuration files [~~http~~://~~trac~~.miranda-ng~~.org~~/~~browser~~/~~trunk~~/plugins/PackUpdater/Docs/Templates here].		You can find sample configuration files [https://github.com/miranda-ng/miranda-ng/tree/master/plugins/PackUpdater/Docs/Templates here].

	# Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.		# Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.

RMN: list markup

2016-01-02T12:27:35Z

list markup

← Older revision		Revision as of 15:27, 2 January 2016
Line 6:		Line 6:
	You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Templates here].		You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Templates here].

	1. Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.		# Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.
			#; Variables in <tt>Autoexec_PackUpdater.ini</tt>
	; Variables in <tt>Autoexec_PackUpdater.ini</tt>		#* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in {{Menu\|Events\|Pack updates}}.
	* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in {{Menu\|Events\|Pack updates}}.		#* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>File1.ini</tt>) is stored.
	* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>File1.ini</tt>) is stored.		#* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.
	* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.		#* <tt>File_x_CurrentVersion</tt> and <tt>File_x_LastVersion</tt> where
	* <tt>File_x_CurrentVersion</tt> and <tt>File_x_LastVersion</tt> where		#** <tt>x</tt> is a serial number of file beginning with <tt>1</tt>
	** <tt>x</tt> is a serial number of file beginning with <tt>1</tt>		#** <tt>CurrentVersion</tt> – set it to 1.0.0 (or any other you like) and don't change it any more
	** <tt>CurrentVersion</tt> – set it to 1.0.0 (or any other you like) and don't change it any more		#** <tt>LastVersion</tt> – the same.
	** <tt>LastVersion</tt> – the same.		# Create file with information about versions (<tt>File1.ini</tt>), one for all files to check.
			#; Options of <tt>File1.ini</tt>
	2. Create file with information about versions (<tt>File1.ini</tt>), one for all files to check.		#* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.
			#* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).
	; Options of <tt>File1.ini</tt>		#* <tt>Message</tt> – the message that user will see when plugin finds new version.
	* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.		#* <tt>DownloadURL</tt> – URL of update file (pack setup).
	* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).		#* <tt>DiskFileName</tt> – name of file saved on user's PC.
	* <tt>Message</tt> – the message that user will see when plugin finds new version.		#* <tt>FileType</tt> – type of file. Defines final destination of file:
	* <tt>DownloadURL</tt> – URL of update file (pack setup).		#** 1 – pack
	* <tt>DiskFileName</tt> – name of file saved on user's PC.		#** 2 – plugin (will be installed into <tt>Plugins</tt> folder)
	* <tt>FileType</tt> – type of file. Defines final destination of file:		#** 3 – icon set (will be installed into <tt>Icons</tt> folder)
	** 1 – pack		#** 4 – files in Miranda root folder
	** 2 – plugin (will be installed into <tt>Plugins</tt> folder)		#* <tt>Descr</tt> – description to show in update list.
	** 3 – icon set (will be installed into <tt>Icons</tt> folder)		#* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.
	** 4 – files in Miranda root folder		#* <tt>AdvFolder</tt> (optional) – sets subfolder in the folder defined by <tt>FileType</tt>.
	* <tt>Descr</tt> – description to show in update list.		#* <tt>Force</tt> (optional) – to update a non-existent file, i.e. add file which is not present in current Miranda installation.
	* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.		# Upload your updates and file with information on server.
	* <tt>AdvFolder</tt> (optional) – sets subfolder in the folder defined by <tt>FileType</tt>.
	* <tt>Force</tt> (optional) – to update a non-existent file, i.e. add file which is not present in current Miranda installation.

	3. Upload your updates and file with information on server.

GBot: {{Menu}} used

2015-12-26T13:31:30Z

{{Menu}} used

← Older revision		Revision as of 16:31, 26 December 2015
Line 9:		Line 9:

	; Variables in <tt>Autoexec_PackUpdater.ini</tt>		; Variables in <tt>Autoexec_PackUpdater.ini</tt>
	* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in ''Events → Pack updates''.		* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in {{Menu\|Events\|Pack updates}}.
	* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>File1.ini</tt>) is stored.		* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>File1.ini</tt>) is stored.
	* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.		* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.

RMN at 06:48, 10 August 2015

2015-08-10T06:48:59Z

← Older revision		Revision as of 09:48, 10 August 2015
Line 19:		Line 19:
	2. Create file with information about versions (<tt>File1.ini</tt>), one for all files to check.		2. Create file with information about versions (<tt>File1.ini</tt>), one for all files to check.

	;Options of <tt>File1.ini</tt>		; Options of <tt>File1.ini</tt>
	* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.		* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.
	* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).		* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).
Line 27:		Line 27:
	* <tt>FileType</tt> – type of file. Defines final destination of file:		* <tt>FileType</tt> – type of file. Defines final destination of file:
	** 1 – pack		** 1 – pack
	** 2 – plugin (will be installed into <tt>Plugins</tt> folder		** 2 – plugin (will be installed into <tt>Plugins</tt> folder)
	** 3 – icon set (will be installed into <tt>Icons</tt> folder)		** 3 – icon set (will be installed into <tt>Icons</tt> folder)
	** 4 – files in Miranda root folder		** 4 – files in Miranda root folder
Line 35:		Line 35:
	* <tt>Force</tt> (optional) – to update a non-existent file, i.e. add file which is not present in current Miranda installation.		* <tt>Force</tt> (optional) – to update a non-existent file, i.e. add file which is not present in current Miranda installation.

	3. Upload file with information ~~and updates~~ on server.		3. Upload your updates and file with information on server.


	== How it works ==		== How it works ==
	Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.		Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.

	First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:		First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:
	* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.		* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.

RMN: final version, needs review

2015-08-09T20:45:55Z

final version, needs review

← Older revision		Revision as of 23:45, 9 August 2015
Line 5:		Line 5:
	== Usage ==		== Usage ==
	You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Templates here].		You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Templates here].

	1. Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.		1. Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.

	; Variables in <tt>Autoexec_PackUpdater.ini</tt>		; Variables in <tt>Autoexec_PackUpdater.ini</tt>
	* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in ''Events → Pack updates''.		* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in ''Events → Pack updates''.
	* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>~~file1~~.ini</tt>) is stored.		* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>File1.ini</tt>) is stored.
	* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.		* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.
	* <tt>~~File_x_~~</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>		* <tt>File_x_CurrentVersion</tt> and <tt>File_x_LastVersion</tt> where
	** <tt>CurrentVersion</tt> – set it to 1.0.0 (or any other you like) and don't change it any more.		** <tt>x</tt> is a serial number of file beginning with <tt>1</tt>
			** <tt>CurrentVersion</tt> – set it to 1.0.0 (or any other you like) and don't change it any more
	** <tt>LastVersion</tt> – the same.		** <tt>LastVersion</tt> – the same.

	2. Create file with information about versions (<tt>~~file1~~.ini</tt>), one for all files to check.		2. Create file with information about versions (<tt>File1.ini</tt>), one for all files to check.

	;Options of <tt>~~file1~~.ini</tt>		;Options of <tt>File1.ini</tt>
	* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.		* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.
	* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).		* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).
	* <tt>Message</tt> – ~~description~~ that user will see when plugin finds new version.		* <tt>Message</tt> – the message that user will see when plugin finds new version.
	* <tt>DownloadURL</tt> – URL of update file.		* <tt>DownloadURL</tt> – URL of update file (pack setup).
	* <tt>DiskFileName</tt> – name of file saved on user's PC.		* <tt>DiskFileName</tt> – name of file saved on user's PC.
	* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.
	* <tt>Descr</tt> – description to show in update list.
	* <tt>FileType</tt> – type of file. Defines final destination of file:		* <tt>FileType</tt> – type of file. Defines final destination of file:
	** 1 – pack		** 1 – pack
Line 30:		Line 30:
	** 3 – icon set (will be installed into <tt>Icons</tt> folder)		** 3 – icon set (will be installed into <tt>Icons</tt> folder)
	** 4 – files in Miranda root folder		** 4 – files in Miranda root folder
			* <tt>Descr</tt> – description to show in update list.
			* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.
	* <tt>AdvFolder</tt> (optional) – sets subfolder in the folder defined by <tt>FileType</tt>.		* <tt>AdvFolder</tt> (optional) – sets subfolder in the folder defined by <tt>FileType</tt>.
	* <tt>Force</tt> (optional) – to update non-existent ~~files~~, i.e. add ~~files~~ which ~~are~~ not present in current Miranda installation.		* <tt>Force</tt> (optional) – to update a non-existent file, i.e. add file which is not present in current Miranda installation.

	3. Upload file with information and updates on server.		3. Upload file with information and updates on server.
Line 40:		Line 42:
	First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:		First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:
	* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.		* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.
	* b) in normal mode plugin ~~displays a~~ message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.		* b) in normal mode plugin shows the message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.

	{{PluginGroups}}		{{PluginGroups}}

RMN at 20:25, 9 August 2015

2015-08-09T20:25:57Z

← Older revision		Revision as of 23:25, 9 August 2015
Line 3:		Line 3:


	== ~~How it works~~ ==		== Usage ==
	~~Plugin has two modes~~: ~~silent and normal~~. ~~Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked~~.		You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Templates here].
	~~First, plugin downloads the version information file and compares the "local" version (~~<tt>~~File_x_CurrentVersion~~</tt> ~~from~~ profile~~) with the "remote" one~~ (~~<tt>FileVersion</tt>)~~. ~~If they differ, than:~~		1. Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. Add strings needed for plugin (e.g. descriptions of update components) to your <tt>langpack_*.txt</tt>.
	* a) ~~in silent mode plugin checks the value of~~ <tt>~~LastVersion</tt> and if it differs from <tt>FileVersion~~</tt>~~, shows the message about the update. If not, there are no messages.~~
	* b) in normal mode plugin displays a message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.

			; Variables in <tt>Autoexec_PackUpdater.ini</tt>
			* <tt>AutoUpdate</tt> – check updates automatically on Miranda startup. Can be configured in ''Events → Pack updates''.
			* <tt>File_VersionURL</tt> – URL where file with information about versions for all files (<tt>file1.ini</tt>) is stored.
			* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but in most cases it is enough to check only pack setup file.
			* <tt>File_x_</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>
			** <tt>CurrentVersion</tt> – set it to 1.0.0 (or any other you like) and don't change it any more.
			** <tt>LastVersion</tt> – the same.

	~~== Usage ==~~		2. Create file with information about versions (<tt>file1.ini</tt>), one for all files to check.
	~~You can find sample configuration files [http://trac~~.~~miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Tamplates here].~~
	~~: 1. Import settings from <tt>Autoexec_PackUpdater.ini</tt> to profile. The~~ <tt>file1.ini</tt> is for ~~your updates server. Add strings needed for plugin (e.g. update components descriptions)~~ to ~~your <tt>langpack_*.txt</tt>~~.

	~~Variables in <tt>Autoexec_PackUpdater.ini</tt>:~~		;Options of <tt>file1.ini</tt>
	* <tt>AutoUpdate</tt> – check updates automatically with Miranda startup. configured in Events->Pack updates		* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file beginning with <tt>1</tt>. Must match the number in profile.
	* <tt>File_VersionURL</tt> – URL where saved file with information about versions of all files (file1.ini)		* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack).
	* <tt>FileCount</tt> – number of files to check updates for. Plugin supports checking for several files, but most time is only one (Pack setup file)		* <tt>Message</tt> – description that user will see when plugin finds new version.
	* <tt>[File_x_]</tt> where <tt>х</tt> is a serial number of file begining from <tt>1</tt>		* <tt>DownloadURL</tt> – URL of update file.
	** <tt>CurrentVersion</tt> – sets 1.0.0 (or another what you wants) and don't change any more
	** <tt>LastVersion</tt> – the same

	~~: 2. Create file with information about versions (<tt>file1.ini</tt>). One for all files to check.~~
	Options of <tt>file1.ini</tt>:
	* Handle <tt>[FileInfo_х]</tt> where <tt>х</tt> is a serial number of file ~~begining from~~ <tt>1</tt> ~~(must~~ match the number in profile)
	* <tt>FileVersion</tt> – current version of file (i.e. version of file in new pack)
	* <tt>Message</tt> – description that user will see when plugin finds new version
	* <tt>DownloadURL</tt> – URL of ~~Update~~ file
	* <tt>DiskFileName</tt> – name of file saved on user's PC.		* <tt>DiskFileName</tt> – name of file saved on user's PC.
	* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.		* <tt>InfoURL</tt> (optional) – sets the URL to be opened by click on ''See information'' button in update message box.
Line 39:		Line 33:
	* <tt>Force</tt> (optional) – to update non-existent files, i.e. add files which are not present in current Miranda installation.		* <tt>Force</tt> (optional) – to update non-existent files, i.e. add files which are not present in current Miranda installation.

	: 3. Upload file with information and updates on server.		3. Upload file with information and updates on server.


			== How it works ==
			Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.
			First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, then:
			* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.
			* b) in normal mode plugin displays a message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.

	{{PluginGroups}}		{{PluginGroups}}

RMN at 19:57, 9 August 2015

2015-08-09T19:57:10Z

@@ Line 6: / Line 6: @@
 Plugin has two modes: silent and normal. Silent mode is used to check for updates on startup, normal mode is used when menu item is clicked.
 First, plugin downloads the version information file and compares the "local" version (<tt>File_x_CurrentVersion</tt> from profile) with the "remote" one (<tt>FileVersion</tt>). If they differ, than:
-* a) in silent mode plugin checks the value <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.
+* a) in silent mode plugin checks the value of <tt>LastVersion</tt> and if it differs from <tt>FileVersion</tt>, shows the message about the update. If not, there are no messages.
 * b) in normal mode plugin displays a message in any case. If a user downloaded an update but decided not to install it, the update is still considered to be installed.
 == Usage ==
-Import settings from Autoexec_PackUpdater.ini to profile and for server (file1.ini) are in Tamplates folder. Probably full langpack in this folder too.
+You can find sample configuration files [http://trac.miranda-ng.org/browser/trunk/plugins/PackUpdater/Docs/Tamplates here].
-. Add in your langpack_*.txt strings needed for plugin.
+Variables in <tt>Autoexec_PackUpdater.ini</tt>:
-Variables in Autoexec_PackUpdater.ini:
+: 2. Create file with information about versions (<tt>file1.ini</tt>). One for all files to check.
-	FileCount - number of files for witch needs to check updates. Plugin supports checking for several files, but most time is only one (Pack setup file)
+: 3. Upload file with information and updates on server.
 {{PluginGroups}}

RMN: from readme, 1st approach

2015-08-09T18:51:19Z

from readme, 1st approach

@@ Line 1: / Line 1: @@
 {{PluginCard}}
-Simple updater for Miranda NG premodified packs.
+Simple updater for Miranda NG premodified packs. Plugin may be interesting for pack authors who want to automate the process of updating of their packs.
 {{PluginGroups}}