Archive:Script library - Revision history

Karellen at 22:55, 16 December 2020

2020-12-16T22:55:09Z

← Older revision		Revision as of 22:55, 16 December 2020
Line 1:		Line 1:
	==What Kodi requires for your addon==		==What Kodi requires for your addon==
	For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-on development~~\|here]]~~ for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See Add-on development for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml" enclose="div">		<syntaxhighlight lang="xml" enclose="div">
Line 43:		Line 43:
	== Interacting with XBMC ==		== Interacting with XBMC ==
	Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the xbmcaddon module.		Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the xbmcaddon module.

	~~[[Category:Add-ons]]~~

Karellen: Karellen moved page Script library to Archive:Script library without leaving a redirect: Duplicate of https://kodi.wiki/view/Script_sources

2020-12-16T22:54:35Z

Karellen moved page Script library to Archive:Script library without leaving a redirect: Duplicate of https://kodi.wiki/view/Script_sources

← Older revision	Revision as of 22:54, 16 December 2020
(No difference)

Karellen: Text replacement - "xbmcaddon module" to "xbmcaddon module"

2020-07-22T01:00:53Z

Text replacement - "xbmcaddon module" to "xbmcaddon module"

← Older revision		Revision as of 01:00, 22 July 2020
Line 42:		Line 42:

	== Interacting with XBMC ==		== Interacting with XBMC ==
	Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the [[xbmcaddon module]].		Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the xbmcaddon module.

	[[Category:Add-ons]]		[[Category:Add-ons]]

Karellen at 06:39, 11 July 2020

2020-07-11T06:39:38Z

← Older revision		Revision as of 06:39, 11 July 2020
Line 1:		Line 1:
	==What Kodi requires for your addon==		==What Kodi requires for your addon==
	For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-~~ons for XBMC (Developement)~~\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-on development\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml" enclose="div">		<syntaxhighlight lang="xml" enclose="div">

Ned Scott: /* What XBMC requires for your addon */

2015-06-17T21:57:17Z

What XBMC requires for your addon

← Older revision		Revision as of 21:57, 17 June 2015
Line 1:		Line 1:
	==What ~~XBMC~~ requires for your addon==		==What Kodi requires for your addon==
	For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

Ned Scott: Ned Scott moved page Script Library to Script library

2015-06-17T21:57:04Z

Ned Scott moved page Script Library to Script library

← Older revision		Revision as of 21:57, 17 June 2015
(No difference)

NedBot: Robot: Substituting template: Name

2014-06-05T20:19:44Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:19, 5 June 2014
Line 1:		Line 1:
	==What ~~{{name}}~~ requires for your addon==		==What XBMC requires for your addon==
	For ~~{{name}}~~ to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for ~~{{name}}~~ (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends ~~{{name}}~~ via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml" enclose="div">		<syntaxhighlight lang="xml" enclose="div">
Line 41:		Line 41:
	</syntaxhighlight>		</syntaxhighlight>

	== Interacting with ~~{{name}}~~ ==		== Interacting with XBMC ==
	Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. ~~{{name}}~~ then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the [[xbmcaddon module]].		Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the [[xbmcaddon module]].

	[[Category:Add-ons]]		[[Category:Add-ons]]

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:15:32Z

Bot: Automated text replacement (- XBMC + {{name}} )

← Older revision		Revision as of 01:15, 5 June 2014
Line 1:		Line 1:
	==What ~~XBMC~~ requires for your addon==		==What {{name}} requires for your addon==
	For ~~XBMC~~ to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for ~~XBMC~~ (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends ~~XBMC~~ via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For {{name}} to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for {{name}} (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends {{name}} via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml" enclose="div">		<syntaxhighlight lang="xml" enclose="div">
Line 41:		Line 41:
	</syntaxhighlight>		</syntaxhighlight>

	== Interacting with ~~XBMC~~ ==		== Interacting with {{name}} ==
	Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. ~~XBMC~~ then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the [[xbmcaddon module]].		Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. {{name}} then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getLocalizedString''' function in the [[xbmcaddon module]].

	[[Category:Add-ons]]		[[Category:Add-ons]]

NedBot: Bot: automated adding of 'enclose="div"' to syntaxhighlight

2014-03-14T06:50:25Z

Bot: automated adding of 'enclose="div"' to syntaxhighlight

← Older revision		Revision as of 06:50, 14 March 2014
Line 2:		Line 2:
	For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml" enclose="div">
	<extension point="xbmc.python.library"		<extension point="xbmc.python.library"
	library="default.py" />		library="default.py" />
Line 20:		Line 20:

	Example of "xbmc.python.library":		Example of "xbmc.python.library":
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml" enclose="div">
	<?xml version="1.0" encoding="UTF-8" standalone="yes"?>		<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
	<addon id="script.recentlyadded"		<addon id="script.recentlyadded"

NedBot: Bot: Automated text replacement (-class="wikitable" +class="prettytable" & -Available Tags +Available tags & - +)

2014-03-14T06:09:44Z

Bot: Automated text replacement (-class="wikitable" +class="prettytable" & -Available Tags +Available tags & -<source +<syntaxhighlight & -</source> +</syntaxhighlight>)

← Older revision		Revision as of 06:09, 14 March 2014
Line 2:		Line 2:
	For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)\|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.library extension point. The layout of the XML describing this extension point is as follows:

	<~~source~~ lang="xml">		<syntaxhighlight lang="xml">
	<extension point="xbmc.python.library"		<extension point="xbmc.python.library"
	library="default.py" />		library="default.py" />
	</~~source~~>		</syntaxhighlight>

	list of extension points and their explanation:		list of extension points and their explanation:
Line 20:		Line 20:

	Example of "xbmc.python.library":		Example of "xbmc.python.library":
	<~~source~~ lang="xml">		<syntaxhighlight lang="xml">
	<?xml version="1.0" encoding="UTF-8" standalone="yes"?>		<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
	<addon id="script.recentlyadded"		<addon id="script.recentlyadded"
Line 39:		Line 39:
	</addon>		</addon>

	</~~source~~>		</syntaxhighlight>

	== Interacting with XBMC ==		== Interacting with XBMC ==