Plugin sources - Revision history

Gade: /* Interacting with Kodi */

2022-04-14T00:48:48Z

Interacting with Kodi

← Older revision		Revision as of 00:48, 14 April 2022
Line 19:		Line 19:

	== Interacting with Kodi ==		== Interacting with Kodi ==
	The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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~~. '''N.B.''' From Kodi 19 onwards, strings.po has been replaced with [[Language_support#What_is_strings.po\|strings.po]]~~.		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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/resurce.language.<name_of_language>/strings.po) which associates integer id's with each label. Kodi 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.

	Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the xbmcaddon module.		Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the xbmcaddon module.

Gade: /* Interacting with Kodi */

2022-04-14T00:47:10Z

Interacting with Kodi

← Older revision		Revision as of 00:47, 14 April 2022
Line 19:		Line 19:

	== Interacting with Kodi ==		== Interacting with Kodi ==
	The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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. '''N.B.''' From Kodi 19 onwards, strings.~~xml~~ has been replaced with [[Language_support#What_is_strings.po\|strings.po]].		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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. '''N.B.''' From Kodi 19 onwards, strings.po has been replaced with [[Language_support#What_is_strings.po\|strings.po]].

	Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the xbmcaddon module.		Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the xbmcaddon module.

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

2020-07-22T01:00:43Z

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

← Older revision		Revision as of 01:00, 22 July 2020
Line 21:		Line 21:
	The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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. '''N.B.''' From Kodi 19 onwards, strings.xml has been replaced with [[Language_support#What_is_strings.po\|strings.po]].		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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. '''N.B.''' From Kodi 19 onwards, strings.xml has been replaced with [[Language_support#What_is_strings.po\|strings.po]].

	Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].		Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the xbmcaddon module.

	If your plugin can provide several content types, Kodi will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.		If your plugin can provide several content types, Kodi will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.

Leopheard: /* Interacting with Kodi */

2019-08-04T04:56:13Z

Interacting with Kodi

← Older revision		Revision as of 04:56, 4 August 2019
Line 19:		Line 19:

	== Interacting with Kodi ==		== Interacting with Kodi ==
	The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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.		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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. '''N.B.''' From Kodi 19 onwards, strings.xml has been replaced with [[Language_support#What_is_strings.po\|strings.po]].

	Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].		Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].

Ronie: /* What Kodi requires for your add-on */

2018-02-25T23:51:03Z

What Kodi requires for your add-on

← Older revision		Revision as of 23:51, 25 February 2018
Line 7:		Line 7:

	== What Kodi requires for your add-on ==		== What Kodi requires for your add-on ==
	For Kodi to know what to do with your add-on, we require your ~~script~~, and an addon.xml file which describes your plugin source. 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 Kodi via the xbmc.python.pluginsource extension point. The layout of the XML describing this extension point is as follows:		For Kodi to know what to do with your add-on, we require your plugin, and an addon.xml file which describes your plugin source. 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 Kodi via the xbmc.python.pluginsource extension point. The layout of the XML describing this extension point is as follows:

	<syntaxhighlight lang="xml" enclose="div">		<syntaxhighlight lang="xml" enclose="div">
	<extension point="xbmc.python.pluginsource"		<extension point="xbmc.python.pluginsource"
	library="~~myscript~~.py">		library="myplugin.py">
	<provides>image video</provides>		<provides>image video</provides>
	</extension>		</extension>
	</syntaxhighlight>		</syntaxhighlight>

	The library attribute provides the file of the python ~~script~~ that contains the main entry point of your ~~script~~. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.		The library attribute provides the file of the python plugin that contains the main entry point of your plugin. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.

	== Interacting with Kodi ==		== Interacting with Kodi ==

Ronie: /* Basic overview */

2018-02-25T23:50:28Z

Basic overview

← Older revision		Revision as of 23:50, 25 February 2018
Line 4:		Line 4:

	== Basic overview ==		== Basic overview ==
	When the user clicks on your plugin source, your python ~~script~~ gets called, allowing you to fetch a listing of media and return it for Kodi to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your ~~script~~ will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.		When the user clicks on your plugin source, your python plugin gets called, allowing you to fetch a listing of media and return it for Kodi to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your plugin will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.

	== What Kodi requires for your add-on ==		== What Kodi requires for your add-on ==

Ronie: /* Interacting with Kodi */

2018-02-25T22:32:41Z

Interacting with Kodi

← Older revision		Revision as of 22:32, 25 February 2018
Line 19:		Line 19:

	== Interacting with Kodi ==		== Interacting with Kodi ==
	The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your ~~scripts~~ to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. 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. Kodi 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.		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your plugin to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. Given that your plugin 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. Kodi 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.

	Your ~~script~~ only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].		Your plugin only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].

	If your plugin can provide several content types, Kodi will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.		If your plugin can provide several content types, Kodi will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.


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

Ned Scott: xbmc -> kodi

2016-02-19T21:35:19Z

xbmc -> kodi

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

2015-06-17T21:53:25Z

What XBMC requires for your add-on

← Older revision		Revision as of 21:53, 17 June 2015
Line 6:		Line 6:
	When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for XBMC to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.		When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for XBMC to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.

	== 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 which describes your plugin source. 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.pluginsource 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 which describes your plugin source. 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.pluginsource extension point. The layout of the XML describing this extension point is as follows:

NedBot: Robot: Substituting template: Name

2014-06-05T20:19:18Z

Robot: Substituting template: Name

← Older revision		Revision as of 21:35, 19 February 2016
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}		{{mininav\|[[Development]]\|[[Add-on development]]\|[[Python development]]}}

	Plugin sources are [[Add-~~ons for XBMC (Developement)~~\|add-ons for ~~XBMC~~]] that provide a media listing for the user. They are currently written in python, and can provide video, music, image or executable content. Once a user installs your plugin source, it will automatically show up in the appropriate section(s) within ~~XBMC~~ based on the content it provides.		Plugin sources are [[Add-on development\|add-ons for Kodi]] that provide a media listing for the user. They are currently written in python, and can provide video, music, image or executable content. Once a user installs your plugin source, it will automatically show up in the appropriate section(s) within Kodi based on the content it provides.

	== Basic overview ==		== Basic overview ==
	When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for ~~XBMC~~ to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.		When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for Kodi to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.

	== 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 which describes your plugin source. 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.pluginsource extension point. The layout of the XML describing this extension point is as follows:		For Kodi to know what to do with your add-on, we require your script, and an addon.xml file which describes your plugin source. 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 Kodi via the xbmc.python.pluginsource 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 18:		Line 18:
	The library attribute provides the file of the python script that contains the main entry point of your script. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.		The library attribute provides the file of the python script that contains the main entry point of your script. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.

	== Interacting with ~~XBMC~~ ==		== Interacting with Kodi ==
	The main form of interacting with ~~XBMC~~ will be parsing what ~~XBMC~~ feeds you in terms of arguments to your scripts to find out what "folder" the user wants to retrieve, and then returning items to ~~XBMC~~ as you construct them. 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.		The main form of interacting with Kodi will be parsing what Kodi feeds you in terms of arguments to your scripts to find out what "folder" the user wants to retrieve, and then returning items to Kodi as you construct them. 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. Kodi 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.

	Your script only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to ~~XBMC~~ (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].		Your script only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to Kodi (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].

	If your plugin can provide several content types, ~~xbmc~~ will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.		If your plugin can provide several content types, Kodi will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.

← 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]]}}

	Plugin sources are [[Add-ons for ~~{{name}}~~ (Developement)\|add-ons for XBMC]] that provide a media listing for the user. They are currently written in python, and can provide video, music, image or executable content. Once a user installs your plugin source, it will automatically show up in the appropriate section(s) within ~~{{name}}~~ based on the content it provides.		Plugin sources are [[Add-ons for XBMC (Developement)\|add-ons for XBMC]] that provide a media listing for the user. They are currently written in python, and can provide video, music, image or executable content. Once a user installs your plugin source, it will automatically show up in the appropriate section(s) within XBMC based on the content it provides.

	== Basic overview ==		== Basic overview ==
	When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for ~~{{name}}~~ to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.		When the user clicks on your plugin source, your python script gets called, allowing you to fetch a listing of media and return it for XBMC to display. You may return either media items directly (for immediate playback) or may return folder items that contain links back into your plugin source. When the user clicks on a media item it'll start playing straight away, just like any other media. When the user clicks on a folder that you provide, your script will be called again with information on what folder item was clicked on given in the arguments. You may then return a different listing of media content and folders as required.

	== 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 which describes your plugin source. 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.pluginsource 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 which describes your plugin source. 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.pluginsource 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 18:		Line 18:
	The library attribute provides the file of the python script that contains the main entry point of your script. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.		The library attribute provides the file of the python script that contains the main entry point of your script. The <provides> element is a whitespace separated list of image, video, audio, executable. There is a [https://github.com/xbmc/xbmc/blob/master/addons/xbmc.python/pluginsource.xsd schema available here] to check you have your XML correctly defined.

	== Interacting with ~~{{name}}~~ ==		== Interacting with XBMC ==
	The main form of interacting with ~~{{name}}~~ will be parsing what ~~{{name}}~~ feeds you in terms of arguments to your scripts to find out what "folder" the user wants to retrieve, and then returning items to ~~{{name}}~~ as you construct them. 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.		The main form of interacting with XBMC will be parsing what XBMC feeds you in terms of arguments to your scripts to find out what "folder" the user wants to retrieve, and then returning items to XBMC as you construct them. 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.

	Your script only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to ~~{{name}}~~ (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].		Your script only runs while it's retrieving a listing - once it has finished the listing it is terminated. Thus, if you wish to store state information, you can do so either in the URLs you return to XBMC (for different folders for instance) or by storing information in a settings file. In addition, you may have particular configuration settings for your addon which can also be accessed via the settings functions in the [[xbmcaddon module]].

	If your plugin can provide several content types, xbmc will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.		If your plugin can provide several content types, xbmc will pass a 'content_type' parameter to the plugin when listing the root directory. This can be used to only return content of the requested type.