Plugin:TabSRMM/Using skins - Revision history

Dart Raiden at 23:07, 27 October 2022

2022-10-27T23:07:41Z

← Older revision		Revision as of 02:07, 28 October 2022
Line 43:		Line 43:
	</translate>		</translate>

	[[Category:Tutorials]]		[[Category:Tutorials{{#translation:}}\|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Dart Raiden at 23:40, 26 September 2022

2022-09-26T23:40:27Z

← Older revision		Revision as of 02:40, 27 September 2022
Line 22:		Line 22:

	<!--T:7-->		<!--T:7-->
	Simply select the desired skin from the list and it will be loaded. You can click the {{Button\|Rescan}} button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .~~TSK~~ file, but TabSRMM 3 has also the possibility to read a custom name from the <tt>.tsk</tt>. The <tt>[Global]</tt> section of the skin definition can have an (optional) <tt>Name=</tt> entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.		Simply select the desired skin from the list and it will be loaded. You can click the {{Button\|Rescan}} button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the <tt>.tsk</tt> file, but TabSRMM 3 has also the possibility to read a custom name from the <tt>.tsk</tt>. The <tt>[Global]</tt> section of the skin definition can have an (optional) <tt>Name=</tt> entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.

	<!--T:8-->		<!--T:8-->

Dart Raiden at 22:52, 26 September 2022

2022-09-26T22:52:08Z

← Older revision		Revision as of 01:52, 27 September 2022
Line 38:		Line 38:

	<!--T:13-->		<!--T:13-->
	* [[../Skinning\|Skinning basics]]		* [[Plugin:TabSRMM/Skinning\|Skinning basics]]
	* [[../Skinning_format\|Detailed description about the skin format]]		* [[Plugin:TabSRMM/Skinning_format\|Detailed description about the skin format]]
	* [[../Theme\|Themes vs skins]]		* [[Plugin:TabSRMM/Theme\|Themes vs skins]]
	</translate>		</translate>

	[[Category:Tutorials]]		[[Category:Tutorials]]

Dart Raiden at 22:51, 26 September 2022

2022-09-26T22:51:51Z

← Older revision		Revision as of 01:51, 27 September 2022
Line 28:		Line 28:

	<!--T:9-->		<!--T:9-->
	To unload the skin, select the first entry from the list (<no skin>).		To unload the skin, select the first entry from the list (<tt><no skin></tt>).

	== About relative path names == <!--T:10-->		== About relative path names == <!--T:10-->

Dart Raiden at 22:51, 26 September 2022

2022-09-26T22:51:20Z

← Older revision		Revision as of 01:51, 27 September 2022
Line 10:		Line 10:

	<!--T:3-->		<!--T:3-->
	Any <tt>.tsk</tt> skin definition file which is ~~NOT~~ in a sub folder of the skins root folder won't be found and therefore cannot be activated.		Any <tt>.tsk</tt> skin definition file which is not in a sub folder of the skins root folder won't be found and therefore cannot be activated.

	== The skins root folder == <!--T:4-->		== The skins root folder == <!--T:4-->
Line 19:		Line 19:
	<translate>		<translate>
	<!--T:6-->		<!--T:6-->
	This folder is located in your profile, specifically in <tt>%miranda_userdata%\TabSRMM\skins</tt> (<tt>%miranda_userdata%</tt> is a core-implemented path variable and usually points to your profile folder – the same folder that holds your ~~NAME~~.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.		This folder is located in your profile, specifically in <tt>%miranda_userdata%\TabSRMM\skins</tt> (<tt>%miranda_userdata%</tt> is a core-implemented path variable and usually points to your profile folder – the same folder that holds your <tt>.dat</tt> file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.

	<!--T:7-->		<!--T:7-->
	Simply select the desired skin from the list and it will be loaded. You can click the ~~'''~~Rescan~~'''~~ button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .TSK file, but TabSRMM 3 has also the possibility to read a custom name from the ~~TSK~~. The [Global] section of the skin definition can have an (optional) ~~'''~~Name=~~'''~~ entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.		Simply select the desired skin from the list and it will be loaded. You can click the {{Button\|Rescan}} button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .TSK file, but TabSRMM 3 has also the possibility to read a custom name from the <tt>.tsk</tt>. The <tt>[Global]</tt> section of the skin definition can have an (optional) <tt>Name=</tt> entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.

	<!--T:8-->		<!--T:8-->
	Click ~~'''~~Reload~~'''~~ to reload the currently select skin (for example, when you are modifying a skin and want to force a reload).		Click {{Button\|Reload active skin}} to reload the currently select skin (for example, when you are modifying a skin and want to force a reload).

	<!--T:9-->		<!--T:9-->
	To ~~'''Unload'''~~ the skin, select the first entry from the list (<no skin>).		To unload the skin, select the first entry from the list (<no skin>).

	== About relative path names == <!--T:10-->		== About relative path names == <!--T:10-->

Dart Raiden at 22:49, 26 September 2022

2022-09-26T22:49:09Z

← Older revision		Revision as of 01:49, 27 September 2022
Line 10:		Line 10:

	<!--T:3-->		<!--T:3-->
	Any <tt>.~~TSK~~</tt> skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.		Any <tt>.tsk</tt> skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.

	== The skins root folder == <!--T:4-->		== The skins root folder == <!--T:4-->
Line 19:		Line 19:
	<translate>		<translate>
	<!--T:6-->		<!--T:6-->
	This folder is located in your profile, specifically in ~~'''~~%miranda_userdata%\TabSRMM\skins~~'''~~ (%miranda_userdata% is a core-implemented path variable and usually points to your profile folder – the same folder that holds your NAME.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.		This folder is located in your profile, specifically in <tt>%miranda_userdata%\TabSRMM\skins</tt> (<tt>%miranda_userdata%</tt> is a core-implemented path variable and usually points to your profile folder – the same folder that holds your NAME.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.

	<!--T:7-->		<!--T:7-->

Dart Raiden at 22:48, 26 September 2022

2022-09-26T22:48:45Z

← Older revision		Revision as of 01:48, 27 September 2022
Line 6:		Line 6:
	* only skins in the skin root folder (see below) will be found.		* only skins in the skin root folder (see below) will be found.
	* one skin per folder (or one folder per skin)		* one skin per folder (or one folder per skin)
	* folder name can be chosen freely by you and it must contain the .~~TSK~~ file		* folder name can be chosen freely by you and it must contain the <tt>.tsk</tt> file
	* images can go into a subfolder, but that's optional. It depends on the skin developer.		* images can go into a subfolder, but that's optional. It depends on the skin developer.

	<!--T:3-->		<!--T:3-->
	Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.		Any <tt>.TSK</tt> skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.

	== The skins root folder == <!--T:4-->		== The skins root folder == <!--T:4-->

Dart Raiden at 22:48, 26 September 2022

2022-09-26T22:48:21Z

← Older revision		Revision as of 01:48, 27 September 2022
Line 11:		Line 11:
	<!--T:3-->		<!--T:3-->
	Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.		Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.


	== The skins root folder == <!--T:4-->		== The skins root folder == <!--T:4-->

Dart Raiden: Marked this version for translation

2022-09-25T17:50:36Z

Marked this version for translation

← Older revision		Revision as of 20:50, 25 September 2022
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
	== Basic rules for installing skins ==		== Basic rules for installing skins == <!--T:1-->

			<!--T:2-->
	* only skins in the skin root folder (see below) will be found.		* only skins in the skin root folder (see below) will be found.
	* one skin per folder (or one folder per skin)		* one skin per folder (or one folder per skin)
Line 8:		Line 9:
	* images can go into a subfolder, but that's optional. It depends on the skin developer.		* images can go into a subfolder, but that's optional. It depends on the skin developer.

			<!--T:3-->
	Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.		Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.


	== The skins root folder ==		== The skins root folder == <!--T:4-->
	</translate>		</translate>

	[[File:TabSRMM skin selection.png\|thumb\|<translate>Selecting a skin</translate>]]		[[File:TabSRMM skin selection.png\|thumb\|<translate><!--T:5--> Selecting a skin</translate>]]

	<translate>		<translate>
			<!--T:6-->
	This folder is located in your profile, specifically in '''%miranda_userdata%\TabSRMM\skins''' (%miranda_userdata% is a core-implemented path variable and usually points to your profile folder – the same folder that holds your NAME.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.		This folder is located in your profile, specifically in '''%miranda_userdata%\TabSRMM\skins''' (%miranda_userdata% is a core-implemented path variable and usually points to your profile folder – the same folder that holds your NAME.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin\|Folders\|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.

			<!--T:7-->
	Simply select the desired skin from the list and it will be loaded. You can click the '''Rescan''' button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .TSK file, but TabSRMM 3 has also the possibility to read a custom name from the TSK. The [Global] section of the skin definition can have an (optional) '''Name=''' entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.		Simply select the desired skin from the list and it will be loaded. You can click the '''Rescan''' button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .TSK file, but TabSRMM 3 has also the possibility to read a custom name from the TSK. The [Global] section of the skin definition can have an (optional) '''Name=''' entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.

			<!--T:8-->
	Click '''Reload''' to reload the currently select skin (for example, when you are modifying a skin and want to force a reload).		Click '''Reload''' to reload the currently select skin (for example, when you are modifying a skin and want to force a reload).

			<!--T:9-->
	To '''Unload''' the skin, select the first entry from the list (<no skin>).		To '''Unload''' the skin, select the first entry from the list (<no skin>).

	== About relative path names ==		== About relative path names == <!--T:10-->

			<!--T:11-->
	Because all skins are in your profile folder, relative path names will always be used. When you use the custom folders plugin to set a custom skins root, path names will be relative to this directory. This means you can share a single skin folder structure among multiple profiles by using the {{Plugin\|Folders\|folders plugin}} and properly configuring the skins root folder {{Menu\|Customize\|Folders\|TabSRMM\|Skins path}}.		Because all skins are in your profile folder, relative path names will always be used. When you use the custom folders plugin to set a custom skins root, path names will be relative to this directory. This means you can share a single skin folder structure among multiple profiles by using the {{Plugin\|Folders\|folders plugin}} and properly configuring the skins root folder {{Menu\|Customize\|Folders\|TabSRMM\|Skins path}}.

	== See also ==		== See also == <!--T:12-->

			<!--T:13-->
	* [[../Skinning\|Skinning basics]]		* [[../Skinning\|Skinning basics]]
	* [[../Skinning_format\|Detailed description about the skin format]]		* [[../Skinning_format\|Detailed description about the skin format]]

Dart Raiden: Created page with " == Basic rules for installing skins == * only skins in the skin root folder (see below) will be found. * one skin per folder (or one folder per skin) * folder name can be chosen freely by you and it must contain the .TSK file * images can go into a subfolder, but that's optional. It depends on the skin developer. Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated...."

2022-09-25T17:50:32Z

Created page with "<languages/> <translate> == Basic rules for installing skins == * only skins in the skin root folder (see below) will be found. * one skin per folder (or one folder per skin) * folder name can be chosen freely by you and it must contain the .TSK file * images can go into a subfolder, but that's optional. It depends on the skin developer. Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated...."

New page

<languages/>
<translate>
== Basic rules for installing skins ==

* only skins in the skin root folder (see below) will be found.
* one skin per folder (or one folder per skin)
* folder name can be chosen freely by you and it must contain the .TSK file
* images can go into a subfolder, but that's optional. It depends on the skin developer.

Any TSK skin definition file which is NOT in a sub folder of the skins root folder won't be found and therefore cannot be activated.

== The skins root folder ==
</translate>

[[File:TabSRMM skin selection.png|thumb|<translate>Selecting a skin</translate>]]

<translate>
This folder is located in your profile, specifically in '''%miranda_userdata%\TabSRMM\skins''' (%miranda_userdata% is a core-implemented path variable and usually points to your profile folder – the same folder that holds your NAME.dat file). If you do not want the skins folder in your profile, you can use the {{Plugin|Folders|custom folders plugin}} which allows you to set a different skins root path. For example, you could share a single skin folder with a number of different profiles, so you would only need to install skins once for all your profiles. To make installing skins easier, the skin selection dialog will show you the location of the skins root path and the drop-down list will be automatically populated with all available skins.

Simply select the desired skin from the list and it will be loaded. You can click the '''Rescan''' button to force TabSRMM rescanning the skins folder and find new skins after you install them while keeping the option dialog open. A automatic rescan will happen whenever you open the skin selection dialog, so no restart is required after adding or deleting skins. The name of the skin is derived from the file name of the .TSK file, but TabSRMM 3 has also the possibility to read a custom name from the TSK. The [Global] section of the skin definition can have an (optional) '''Name=''' entry and when such an entry is found, TabSRMM will use it for the name of the skin in the drop-down list. Note that most skins do not have such an entry, because it is a new specification.

Click '''Reload''' to reload the currently select skin (for example, when you are modifying a skin and want to force a reload).

To '''Unload''' the skin, select the first entry from the list (<no skin>).

== About relative path names ==

Because all skins are in your profile folder, relative path names will always be used. When you use the custom folders plugin to set a custom skins root, path names will be relative to this directory. This means you can share a single skin folder structure among multiple profiles by using the {{Plugin|Folders|folders plugin}} and properly configuring the skins root folder {{Menu|Customize|Folders|TabSRMM|Skins path}}.

== See also ==

* [[../Skinning|Skinning basics]]
* [[../Skinning_format|Detailed description about the skin format]]
* [[../Theme|Themes vs skins]]
</translate>

[[Category:Tutorials]]