== Skin Organization when creating new widget ==

To create your own new skin for your own new widget follow the instructions below.  

You can organize the skin system in your widget in any way you want. The recommended way is to use Flash internal runtime sharing. To use it you should make the following:

Any library elements in your application that you want to define with your skin should be copied to the skin file. After all elements are copied, do the following with every library element:


    1. Select a movie clip, button, graphic symbol, bitmap, or sound in the Library panel and select Properties from
the Library options menu. Click the Advanced button to expand the Properties dialog box.

    2. For Linkage, select "Export for !ActionScript" and "Export in first frame".

    3. Enter an identifier for the symbol, bitmap, or sound in the Identifier. Do not include spaces.

    4. Find the respective element in application library and open Linkage dialog.

    5. For Linkage, select "Import for runtime sharing".

    6. Enter URL: "'''skins/'''".

After all elements in the skin file are done, publish the skin file.

All skin files should be located in the "skins" folder of your widget package. If you use this way of skin organization, you should create an '''index.php''' file in the same folder with the following contents:

{{{
<?
setlocale(LC_ALL, 'EN_US');
header('Expires: ' . gmdate('D, d M Y H:i:s', time()) . ' GMT');
header("Content-Type: application/x-shockwave-flash");
require_once("../../global/inc/header.inc.php");
require_once($sIncPath . "functions.inc.php");
require_once($sIncPath . "apiFunctions.inc.php");
require_once($sIncPath . "xml.inc.php");
$aPathParts = explode("/", $_SERVER['PHP_SELF']);
$iPartsCount = count($aPathParts);
$aResult = getExtraFiles($aPathParts[$iPartsCount-3], $aPathParts[$iPartsCount-2]);
$sFile = $aResult['current'] . "." . $aResult['extension'];
readfile($sFile);
?>
}}}

This file is necessary to define and display skin files according to a user's previous choice saved as a cookie in one's browser.