Running Wimpy off of a "Wimpy Configs" file.
The process of running Wimpy off of an external configuration file is a two-step process.
1. Generate a configs file
2. Generate HTML code to "apply" the config file to the player.
The Customizer tool is used to accomplish both steps. This means that we'll be using the Customizer tool two times, once to generate the config file and the second time to generate the HTML code.
NOTE: When a file named "wimpyConfigs.xml" is located in the same folder as wimpy.php, the settings defined within the "wimpyConfigs.xml" file will automatically be applied to the "default" player when "wimpy.php" is pulled up. For example, if you create a "wimpyConfigs.xml" file, then upload the file to the same folder as wimpy.php, then access wimpy.php directly, all the settings (including the skin" will be applied to the "default" player.
These instructions assume:
- You have already installed (uploaded) Wimpy.
- Are using the "PHP" version. If you are using the ASP or ColdFusion version, replace "wimpy.php" with "wimpy.asp" or "wimpy.cfm" respectively throughout these instructions.
NOTE: If you are running Wimpy off of an XML playlist (e.g. not using wimpy.php/asp/cfm to automatically generate a playlist, ignore step 3.
|
HINT: After uploading a "wimpyConfigs.xml" file to your Wimpy installation folder, then pulling up wimpy.php directly, you can use your browsers "view source" feature to retrieve the necessary HTML code to use the "default" player throughout your site. The HTML code that wimpy.php generates uses javascript to display the player. The javascript used to display the player automatically "applies" the wimpyConfigs.xml" file to the player.
HINT: You can use more than one "wimpyConfigs.xml" file. What's more, you do not have to name the config file "wimpyConfigs.xml." For example, you can have two players on your site, where each player uses a different skin and different settings. Each player can run off of a separate config's file. For example, Player A can use a config file named "player_a_configs.xml" and Player B can use a config file named "player_b_configs.xml." You can use the Customizer tool to generate the necessary HTML code to run a player off of a config file of your choosing (See step # 4). |
3. Check to make sure that Wimpy is working properly by entering the URL to "wimpy.php" into your browsers address bar. If you are running Wimpy off of an XML playlist (e.g. not using wimpy.php/asp/cfm to automatically generate a playlist) ignore this step and continue to step 4.
NOTE: If you only see the Wimpy logo, this indicates that Wimpy is have problems loading the skin or any of the images related to the skin. Be sure to upload any associated background graphics (e.g. skin_name_bkgd,jpg) to the same location as your skin_name.xml file on your server. You also may want to check that you entered the proper URL tot he skin file when using the Customizer tool. You can re-use the Customizer tool to change the URL to the skin, or you can edit the wimpyConfigs.xml file directly using a text editor and changing the <wimpySkin> tag.
|


|