Script lyrics - Revision history

Gade: /* Interacting with XBMC */

2022-04-14T00:45:19Z

Interacting with XBMC

← Older revision		Revision as of 00:45, 14 April 2022
Line 41:		Line 41:

	== 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 '''getString''' 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.po file (in resources/language/<name_of_language>/strings.po) 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 '''getString''' function in the xbmcaddon module.

	== See also ==		== See also ==

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

2020-07-22T01:00:48Z

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

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

	== 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 '''getString''' 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 '''getString''' function in the xbmcaddon module.

	== See also ==		== See also ==

Karellen at 06:38, 11 July 2020

2020-07-11T06:38:56Z

← Older revision		Revision as of 06:38, 11 July 2020
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Add-on ~~development]]\|[[Python~~ development]]}}		{{mininav\|[[Development]]\|[[Add-on development]]}}
	==What Kodi requires for your add-on==		==What Kodi requires for your add-on==
	For XBMC to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your add-on, 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.lyrics 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 45:		Line 45:
	== See also ==		== See also ==
	* [[Add-ons]]		* [[Add-ons]]
	* [[:Category:All add-ons]]
	* [[Unofficial add-on repositories]]		* [[Unofficial add-on repositories]]
	'''Development:'''		'''Development:'''
	* [[Add-on development]]		* [[Add-on development]]
	* [[Addon Settings]]		* [[Addon Settings]]
	* [[Python development]]
	* [[Add-on repositories]]		* [[Add-on repositories]]
	* [[Official add-on repository]]		* [[Official add-on repository]]

	~~[[Category:Python Tutorial]]~~
	[[Category:Python]]		[[Category:Python]]
	~~[[Category:How-to]]~~
	[[Category:Add-on development]]		[[Category:Add-on development]]

Gamester17 at 18:24, 26 October 2018

2018-10-26T18:24:24Z

← Older revision		Revision as of 18:24, 26 October 2018
Line 46:		Line 46:
	* [[Add-ons]]		* [[Add-ons]]
	* [[:Category:All add-ons]]		* [[:Category:All add-ons]]
	* [[~~3rd party~~ add-on repositories]]		* [[Unofficial add-on repositories]]
	'''Development:'''		'''Development:'''
	* [[Add-on development]]		* [[Add-on development]]

Ned Scott: /* What XBMC requires for your add-on */

2015-06-17T21:56:31Z

What XBMC requires for your add-on

← Older revision		Revision as of 21:56, 17 June 2015
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}		{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}
	==What ~~XBMC~~ requires for your add-on==		==What Kodi requires for your add-on==
	For XBMC to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:

NedBot: Robot: Substituting template: Name

2014-06-05T20:19:35Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:19, 5 June 2014
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}		{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}
	==What ~~{{name}}~~ requires for your add-on==		==What XBMC requires for your add-on==
	For ~~{{name}}~~ to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your add-on, 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.lyrics 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 40:		Line 40:
	</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 '''getString''' 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 '''getString''' function in the [[xbmcaddon module]].

	== See also ==		== See also ==

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

2014-06-05T01:15:37Z

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

← Older revision		Revision as of 01:15, 5 June 2014
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}		{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}
	==What ~~XBMC~~ requires for your add-on==		==What {{name}} requires for your add-on==
	For ~~XBMC~~ to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:		For {{name}} to know what to do with your add-on, 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.lyrics 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 40:		Line 40:
	</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 '''getString''' 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 '''getString''' function in the [[xbmcaddon module]].

	== See also ==		== See also ==

NedBot: Robot: Changing Category:Addon Development to Category:Add-on development

2014-04-23T19:11:37Z

Robot: Changing Category:Addon Development to Category:Add-on development

← Older revision		Revision as of 19:11, 23 April 2014
Line 57:		Line 57:
	[[Category:Python]]		[[Category:Python]]
	[[Category:How-to]]		[[Category:How-to]]
	[[Category:~~Addon Development~~]]		[[Category:Add-on development]]

Ned Scott at 01:19, 15 April 2014

2014-04-15T01:19:26Z

← Older revision		Revision as of 01:19, 15 April 2014
Line 56:		Line 56:
	[[Category:Python Tutorial]]		[[Category:Python Tutorial]]
	[[Category:Python]]		[[Category:Python]]
	~~[[Category:Settings]]~~
	[[Category:How-to]]		[[Category:How-to]]
	~~[[Category:Add-ons]]~~
	[[Category:Addon Development]]		[[Category:Addon Development]]
	~~[[Category:Development]]~~

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

2014-03-14T06:50:45Z

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

← Older revision		Revision as of 06:50, 14 March 2014
Line 3:		Line 3:
	For XBMC to know what to do with your add-on, 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.lyrics extension point. The layout of the XML describing this extension point is as follows:		For XBMC to know what to do with your add-on, 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.lyrics 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.lyrics"		<extension point="xbmc.python.lyrics"
	library="default.py" />		library="default.py" />
Line 21:		Line 21:

	Example of "xbmc.python.lyrics":		Example of "xbmc.python.lyrics":
	<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.cu.lyrics"		<addon id="script.cu.lyrics"