Skin development tools: Difference between revisions
Jump to navigation
Jump to search
m (Ned Scott moved page Skin Development Tools to Skin development tools: caps) |
|||
Line 5: | Line 5: | ||
== | == TexturePacker == | ||
{{main|TexturePacker}} | |||
[[File:Basic-package.png]] | [[File:Basic-package.png|left]] | ||
XBMC uses a tool named TexturePacker to compile all images used in a skin into a single file. The benefit of it is that images inside the Textures.xbt will load faster in the skin. This is done by converting all images into a format that take less processing by XBMC when they need to be rendered onto the screen. | XBMC uses a tool named TexturePacker to compile all images used in a skin into a single file. The benefit of it is that images inside the Textures.xbt will load faster in the skin. This is done by converting all images into a format that take less processing by XBMC when they need to be rendered onto the screen. | ||
A common misconception is that TexturPacker will just compress the images into a single file, this if far from the truth, so don't be surprised if the Textures.xbt file is much larger than to total size of all the individual images. |
Revision as of 09:30, 12 March 2014
Development | Add-on development | Skin development | Skin development tools |
Below you will find software that can be useful in Skin Development.
TexturePacker
Main page: TexturePacker
XBMC uses a tool named TexturePacker to compile all images used in a skin into a single file. The benefit of it is that images inside the Textures.xbt will load faster in the skin. This is done by converting all images into a format that take less processing by XBMC when they need to be rendered onto the screen.
A common misconception is that TexturPacker will just compress the images into a single file, this if far from the truth, so don't be surprised if the Textures.xbt file is much larger than to total size of all the individual images.