http://ghostwire.com/aspireui/docs/ 2010-04-05T01:15:55-05:00 http://ghostwire.com/aspireui/docs/ http://ghostwire.com/aspireui/docs/lib/images/favicon.ico text/html 2008-12-20T21:51:56-05:00 http://ghostwire.com/aspireui/docs/skinning/about-skins?rev=1229831516&do=diff Below shows the “CheckBox.png” skin asset from the “classic” theme (blown up here for a closer look): This single image file is used to render the various visual states of the uiCheckBox. The image will be cut up from left-to-right into equal slices representing the states of “up”, “over”, “down”, “disabled”, “selected_up”, “selected_over”, “selected_down”, and “selected_disabled” respectively. The names of these slices are defined in the “rules.xml” file stored in the same folder as the PNG … text/html 2008-12-20T21:42:08-05:00 http://ghostwire.com/aspireui/docs/skinning/about-themes?rev=1229830928&do=diff A theme is a collection of skins, typically with consistent look, stored in the same folder. A theme would also usually have its own set of appropriate text styles declared in a CSS file stored in the same folder. By default, Aspire UI will use the “default” theme, ie the assets stored in the “assets/skins/default” folder. text/html 2009-11-04T05:45:29-05:00 http://ghostwire.com/aspireui/docs/skinning/embedding-skin-assets-deprecated?rev=1257335129&do=diff IMPORTANT NOTE: As of Aspire UI Components Version 1.3.0+, the correct way to embed skin assets would be to pack them into a single binary file using “Amber” (a tool provided in the distribution) and then embedding this file using the [Embed] meta tag. text/html 2010-03-18T06:13:13-05:00 http://ghostwire.com/aspireui/docs/skinning/embedding-skin-assets?rev=1268910793&do=diff Note: Aspire UI Components Version 1.3.0+ is required. This article explains how to embed skin assets into your SWF. Step I: Packing Skin Assets Into A Single Theme File First, you must pack your skin assets into a single binary file using “Amber”. Please see Packing Skin Assets for instructions. text/html 2009-11-04T05:59:38-05:00 http://ghostwire.com/aspireui/docs/skinning/excluding-skin-assets?rev=1257335978&do=diff NOTE: As of Version 1.3.0+, you may compress skin assets into a single binary file. By using the packing tool, “Amber”, provided in the Aspire UI distribution, you can easily exclude skin assets when packing the theme. See Packing Skin Assets text/html 2009-11-04T05:58:21-05:00 http://ghostwire.com/aspireui/docs/skinning/home?rev=1257335901&do=diff * Introduction to Skinning * About Skins * About Themes * Packing Skin Assets * Excluding Skin Assets * Embedding Skin Assets text/html 2009-04-02T22:17:24-05:00 http://ghostwire.com/aspireui/docs/skinning/introduction-to-skinning?rev=1238728644&do=diff The process of customizing the graphical appearance of UI components is termed as skinning. In Aspire UI, a component may be rendered using one or more external PNG bitmap files. These PNG bitmap files are termed as skins. A basic component such as the uiButton would use only a single skin asset, while composite components such as the uiScrollBar would use multiple skin assets. text/html 2010-03-18T06:10:02-05:00 http://ghostwire.com/aspireui/docs/skinning/packing-skin-assets?rev=1268910602&do=diff Note: Aspire UI Components Version 1.3.0+ is required. You may compress skin assets from a theme folder, along with the “rules.xml” file, into one single binary file. This is advantageous for the following reasons: * the overall total payload (bytes to download over the network) is now reduced due to compression;