Using an external configuration file

An external configuration file is useful if you will be using only one "style / skin" and one set of options for all instances of Wasp throughout your site.

Using an external XML configuration file is especially useful if all of the media on your site uses the same options. The resulting HTML code is much smaller because only the configuration file is referenced -- not each and every option.

You may liken the usage of an external configuration file to using a CSS stylesheet. The nice thing about a CSS style sheet is that if you modify the CSS, all the pages that use the CSS are instantly updated.

Likewise, if you use and external XML configuration file, when you modify the config file, all of the Wasp players will instantly update to reflect the new configuration options.

By default, you only need to enter the filename of the config file when rendering the player. If you only use a file name, Wasp will assume that the config file is located in the same folder as the code Wasp files. (e.g. That the config file is located in the same folder as wasp.swf and wasp.js.)

If, however, you enter a full URL to the config file, Wasp will use the designated file.

Here is an example of a config file:

<wimpyConfigs version="2.0">
  <fp>example.html</fp>
  <im>http://www/path/to/poster_graphic.jpg</im>
  <cl>1</cl>
  <ph>260</ph>
  <pw>356</pw>
  <waspSkin>sz_1|1|1^st_1|3|18|E8E8E8|000000</waspSkin>
  <waspJS>wasp.js</waspJS>
  <waspSwf>wasp.swf</waspSwf>
</wimpyConfigs>

Each of the options (indicated by red in the example above) will be applied to all instances of Wasp that use the config file.

The only options that individual instances will not "take on" are:

- width and height ( pw / ph )
- background color ( pageColor )
- poster graphic ( im ) -- unless the code used to display the media does not include a poster graphic.

Refer to the Wasp API or the "Quick Reference" chart for a complete list of all configurable options within Wasp.