Archive:WindowXML - Revision history

Karellen: Karellen moved page WindowXML to Archive:WindowXML without leaving a redirect: Outdated

2020-07-11T02:43:50Z

Karellen moved page WindowXML to Archive:WindowXML without leaving a redirect: Outdated

← Older revision	Revision as of 02:43, 11 July 2020
(No difference)

Karellen at 02:32, 11 July 2020

2020-07-11T02:32:05Z

← Older revision		Revision as of 02:32, 11 July 2020
Line 2:		Line 2:
	{{outdated}}		{{outdated}}

	WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[~~Building Python Scripts~~\|python]] scripters to create dynamic windows from an XML file, just like how Kodi skinners creates windows from XML for Home, Music, Programs windows, and similar to how [https://forum.kodi.tv/showthread.php?tid=21315 GUIBuilder.py] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in Kodi and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in Kodi for creating windows from XML, so it will always use the same XML format/style, as XBMC.		WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Archive:Write_Python_Scripts\|python]] scripters to create dynamic windows from an XML file, just like how Kodi skinners creates windows from XML for Home, Music, Programs windows, and similar to how [https://forum.kodi.tv/showthread.php?tid=21315 GUIBuilder.py] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in Kodi and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in Kodi for creating windows from XML, so it will always use the same XML format/style, as XBMC.

	This page is meant for python scripters using Kodi to create their scripts, not really useful for general users.		This page is meant for python scripters using Kodi to create their scripts, not really useful for general users.
Line 104:		Line 104:
	See CSkinInfo::GetSkinPath in Skininfo.cpp and WindowXML_New in winxml.cpp for the code for how fallback works		See CSkinInfo::GetSkinPath in Skininfo.cpp and WindowXML_New in winxml.cpp for the code for how fallback works

	~~== See also ==~~
	~~'''Development:'''~~
	* [[Add-on development]]
	* [[Skinning]]

	[[Category:~~Skin development~~]]
			[[Category:Development-Archived]]

Davu at 14:51, 16 February 2018

2018-02-16T14:51:34Z

← Older revision		Revision as of 14:51, 16 February 2018
Line 2:		Line 2:
	{{outdated}}		{{outdated}}

	WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how Kodi skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in Kodi and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in Kodi for creating windows from XML, so it will always use the same XML format/style, as XBMC.		WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how Kodi skinners creates windows from XML for Home, Music, Programs windows, and similar to how [https://forum.kodi.tv/showthread.php?tid=21315 GUIBuilder.py] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in Kodi and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in Kodi for creating windows from XML, so it will always use the same XML format/style, as XBMC.

	This page is meant for python scripters using Kodi to create their scripts, not really useful for general users.		This page is meant for python scripters using Kodi to create their scripts, not really useful for general users.

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:59:05Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:59, 4 May 2015
Line 2:		Line 2:
	{{outdated}}		{{outdated}}

	WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how ~~XBMC~~ skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in ~~XBMC~~ and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in ~~XBMC~~ for creating windows from XML, so it will always use the same XML format/style, as XBMC.		WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how Kodi skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in Kodi and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in Kodi for creating windows from XML, so it will always use the same XML format/style, as XBMC.

	This page is meant for python scripters using ~~XBMC~~ to create their scripts, not really useful for general users.		This page is meant for python scripters using Kodi to create their scripts, not really useful for general users.


Line 74:		Line 74:

	== Fallback Explained ==		== Fallback Explained ==
	By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way ~~XBMC~~ media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.		By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way Kodi media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.
	* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname		* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname
	* Step 2) If that wasn't found, check q:\skin\currentskin\pal		* Step 2) If that wasn't found, check q:\skin\currentskin\pal
Line 82:		Line 82:
	* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal		* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal
	Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.		Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.
	'''Note:''' ~~XBMC~~ holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins		'''Note:''' Kodi holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins

	=== Example ===		=== Example ===

NedBot: Robot: Substituting template: Name

2014-06-05T20:13:24Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:13, 5 June 2014
Line 2:		Line 2:
	{{outdated}}		{{outdated}}

	WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how ~~{{name}}~~ skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in ~~{{name}}~~ and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in ~~{{name}}~~ for creating windows from XML, so it will always use the same XML format/style, as XBMC.		WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how XBMC skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in XBMC and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in XBMC for creating windows from XML, so it will always use the same XML format/style, as XBMC.

	This page is meant for python scripters using ~~{{name}}~~ to create their scripts, not really useful for general users.		This page is meant for python scripters using XBMC to create their scripts, not really useful for general users.


Line 74:		Line 74:

	== Fallback Explained ==		== Fallback Explained ==
	By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way ~~{{name}}~~ media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.		By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way XBMC media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.
	* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname		* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname
	* Step 2) If that wasn't found, check q:\skin\currentskin\pal		* Step 2) If that wasn't found, check q:\skin\currentskin\pal
Line 82:		Line 82:
	* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal		* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal
	Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.		Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.
	'''Note:''' ~~{{name}}~~ holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins		'''Note:''' XBMC holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins

	=== Example ===		=== Example ===

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

2014-06-05T01:20:23Z

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

← Older revision		Revision as of 01:20, 5 June 2014
Line 2:		Line 2:
	{{outdated}}		{{outdated}}

	WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how ~~XBMC~~ skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in ~~XBMC~~ and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in ~~XBMC~~ for creating windows from XML, so it will always use the same XML format/style, as XBMC.		WindowXML is a class available in the python scripting side of XBMC. The WindowXML GUI Toolkit is an application framework that allow [[Building Python Scripts\|python]] scripters to create dynamic windows from an XML file, just like how {{name}} skinners creates windows from XML for Home, Music, Programs windows, and similar to how [[GUIBuilder.py]] (a library written in python for XBMC) can take the XML and make a window, how ever it was limited solely to controls that existed in {{name}} and involved having to add extra stuff to the controls in order to give more control over the creation of controls, WindowXML uses the WindowXML class in {{name}} for creating windows from XML, so it will always use the same XML format/style, as XBMC.

	This page is meant for python scripters using ~~XBMC~~ to create their scripts, not really useful for general users.		This page is meant for python scripters using {{name}} to create their scripts, not really useful for general users.


Line 74:		Line 74:

	== Fallback Explained ==		== Fallback Explained ==
	By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way ~~XBMC~~ media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.		By default forceFallback is 'false' so it won't diminish looking in the current skins folder. Note: media doesn't fallback the same way. If an image has the same name as one in the current skin it will use that, this is due to the way {{name}} media/texture handling works. For the 'DefaultSkin' its best to choose names that are unique so it won't conflict with a skin.
	* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname		* Step 1) Looks in q:\skin\currentskin\currentresolution\ for XMLname
	* Step 2) If that wasn't found, check q:\skin\currentskin\pal		* Step 2) If that wasn't found, check q:\skin\currentskin\pal
Line 82:		Line 82:
	* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal		* Step 6) If that wasn't found, check %fallbackpath%\skins\Default\pal
	Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.		Summary, is it will keep 'falling back' until it hopefuly finds it. Its set up so it will always check the pal folder just for consistency.
	'''Note:''' ~~XBMC~~ holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins		'''Note:''' {{name}} holds its skins in a folder call skin, but for in the fallbackpath (typically script folder) use the folder skins

	=== Example ===		=== Example ===

NedBot: Robot: Changing Category:Skin Development to Category:Skin development

2014-04-23T19:03:12Z

Robot: Changing Category:Skin Development to Category:Skin development

← Older revision		Revision as of 19:03, 23 April 2014
Line 109:		Line 109:
	* [[Skinning]]		* [[Skinning]]

	[[Category:Skin ~~Development~~]]		[[Category:Skin development]]

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

2014-03-14T06:53:53Z

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

← Older revision		Revision as of 06:53, 14 March 2014
Line 41:		Line 41:

	=== Base 'FrameWork' for a WindowXML ===		=== Base 'FrameWork' for a WindowXML ===
	<syntaxhighlight lang="python">		<syntaxhighlight lang="python" enclose="div">
	class MyFirstWinXML(xbmcgui.WindowXMLDialog):		class MyFirstWinXML(xbmcgui.WindowXMLDialog):
	def __init__(self,strXMLname, strFallbackPath, strDefaultName, forceFallback):		def __init__(self,strXMLname, strFallbackPath, strDefaultName, forceFallback):

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

2014-03-14T06:14:05Z

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

← Older revision		Revision as of 06:14, 14 March 2014
Line 41:		Line 41:

	=== Base 'FrameWork' for a WindowXML ===		=== Base 'FrameWork' for a WindowXML ===
	<~~source~~ lang="python">		<syntaxhighlight lang="python">
	class MyFirstWinXML(xbmcgui.WindowXMLDialog):		class MyFirstWinXML(xbmcgui.WindowXMLDialog):
	def __init__(self,strXMLname, strFallbackPath, strDefaultName, forceFallback):		def __init__(self,strXMLname, strFallbackPath, strDefaultName, forceFallback):
Line 68:		Line 68:
	pass		pass

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

	== Default Skin ==		== Default Skin ==

>NedBot: Robot: Cosmetic changes

2013-04-27T16:02:16Z

Robot: Cosmetic changes

← Older revision		Revision as of 16:02, 27 April 2013
Line 26:		Line 26:
	* getCurrentListPosition() -- Gets the current position in the Window List		* getCurrentListPosition() -- Gets the current position in the Window List
	* getListItem(int) -- Returns a given ListItem in the WindowList at the specified position		* getListItem(int) -- Returns a given ListItem in the WindowList at the specified position
	* getListSize() -- Returns the number of entries in the WindowList (the size of the WindowLists)		* getListSize() -- Returns the number of entries in the WindowList (the size of the WindowLists)
	* removeItem(itemPosition) -- Removes a specified item based on position in the list from the window list.		* removeItem(itemPosition) -- Removes a specified item based on position in the list from the window list.
	* setCurrentListPosition() -- Set the current position of the Window List		* setCurrentListPosition() -- Set the current position of the Window List
Line 32:		Line 32:
	=== Controls ===		=== Controls ===
	TODO) Write about how to use controls. (A Start)		TODO) Write about how to use controls. (A Start)
	The key to using WindowXML is by id, onClick and onFocus both give you the ID of the control clicked (not a 'control object' like normal Python Windows and Dialogs do. To set visiblity on controls or change labels etc use .getControl(ID) which will return a object of the control type (provided it has a python equivalent). Need to see about having a generic control return if its not, its on the TODO list.		The key to using WindowXML is by id, onClick and onFocus both give you the ID of the control clicked (not a 'control object' like normal Python Windows and Dialogs do. To set visiblity on controls or change labels etc use .getControl(ID) which will return a object of the control type (provided it has a python equivalent). Need to see about having a generic control return if its not, its on the TODO list.

	Important if you don't want to use the WindowLists you still need to remember not to use the ids for other stuff.		Important if you don't want to use the WindowLists you still need to remember not to use the ids for other stuff.
Line 104:		Line 104:
	See CSkinInfo::GetSkinPath in Skininfo.cpp and WindowXML_New in winxml.cpp for the code for how fallback works		See CSkinInfo::GetSkinPath in Skininfo.cpp and WindowXML_New in winxml.cpp for the code for how fallback works

	==See also==		== See also ==
	'''Development:'''		'''Development:'''
	* [[Add-on development]]		* [[Add-on development]]