Running Wimpy on a CD, DVD or PC

When setting up Wimpy for the local file system, you'll have to generate or edit the HTML code by hand. You can use the Customizer Tool as a starting point to create the HTML code needed to embed the player within an HTML page. And you can use Playlister to create an XML playlist based on local files.

The easiest way to go about doing this is to configure the player on a live website. By using the Customizer Tool on a live web site, associated files (such as the skin, start up logo, etc.), player size and playlist options can be set up rather painlessly.

We highly recommend putting all the files associated with Wimpy into ONE folder. If you plan on configuring Wimpy on a live web site, we recommend creating a new folder on your website and then uploading only the files that you need to this newly created folder. The new folder should not have and sub-folders, so you should move any skin files, media files, image files, and any other files associated with Wimpy out of the subfolders and into the main Wimpy folder. This way, you only have to use the "base" file names for all file references (and not a full URL / path). Click here for more information on relative and absolute.

For example, the following files should all be in the same folder:

- myWimpy.html
- wimpy.swf / rave.swf / wasp.swf / wimpy_button.swf
- wimpy.js / rave.js / wasp.js / wimpy_button.js
- playlist.xml
- skin_name.xml (+ andy graphics associated with the skin)
- media.mp3

Once you have everything working OK on your live web site, simply download all the files associated with Wimpy to a local folder, then open each text-base file (XML playlist, javascript and HTML files) and replace the URL to each file with just the file name.

For example, in the HTML code, you'll see references to files such as:

wimpyApp=http://www.yoursite.com/path/to/wimpy/playlist.xml

Change this to:

wimpyApp=playlist.xml

So you can see, we're just removing the "path" to the file and just leaving the file name. Using just a file name (and not including the "path") is known as using a "relative" path. For more information on using "relative" paths see the "Relative & Absolute" page.

Manually creating the HTML code

Alternatively, you can copy and paste the following HTML code into a blank text document, then save the new text document as an "HTML" file (Example: myWimpy.html). Be sure to save the file in the same folder as the core Wimpy files.

<!-- START WIMPY PLAYER CODE -->
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=8,0,0,0" width="480" height="140" id="wimpy3157">
<param name="allowScriptAccess" value="always" />
<param name="movie" value="wimpy.swf" />
<param name="loop" value="false" />
<param name="menu" value="false" />
<param name="quality" value="high" />
<param name="scale" value="noscale" />
<param name="salign" value="lt" />
<param name="bgcolor" value="000000" />
<param name="flashvars" value="wimpyReg= REGISTRATION_CODE_HERE&wimpyApp=playlist.xml&wimpySkin=skin_name.xml&startPlayingOnload=yes&startupLogo=myLogo.jpg" />
<embed src="wimpy.swf" flashvars="wimpyReg=REGISTRATION_CODE_HERE&wimpyApp=playlist.xml&wimpySkin=skin_name.xml&startPlayingOnload=yes&startupLogo=myLogo.jpg" loop="false" menu="false" quality="high" width="480" height="140" scale="noscale" salign="lt" name="wimpy3157" align="center" bgcolor="000000" allowScriptAccess="always" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" />
</object>
<!-- END WIMPY PLAYER CODE -->

The items in red need to be manually edited to their proper values.

The items in green are optional. You can either edit them or delete them. See the API section of the documentation for all of the available options.

NOTE: The HTML code example above uses both an XML playlist. If you plan on using an embedded playlist, replace "wimpyApp=playlist.xml" with "playlist=myfile1.mp3|myfile2.mp3|myfile3.mp3" where each file is separated by a "pipe" character.

NOTE: You'll notice that there are two places to edit each "thing". For example, you'll have to edit the "width" twice, once within the <object> tag and once within the <embed> tag. The reason for this is because the <object> tag is used by Mozilla-based browsers and the <embed> tag is used by Internet Explorer-based browsers.

Again, we recommend placing all of the files associated with Wimpy in the same folder as the core Wimpy files (the wimpy SWF and JS files). This includes the media files, images and skin files and any other file associated with Wimpy. If you must use folders, you'll have to ensure that the reference to files located within sub-folders is correct. You can use "../../../subfolder/file.mp3" and "subfolder/file.mp3" type paths, but this can become complicated for newbies and is only recommended for advanced users. Click here for more information on relative and absolute.

Playlists

You can use an external XML playlist file or an embedded playlist. There is no way to automatically or dynamically list files within Wimpy -- the playlist must be "static" using an XML playlist or an embedded playlist.

If you plan on using an XML playlist, you should first create an XML playlist using Playlister, then upload it to your Wimpy installation folder. You will not have to upload the media files if you plan on using an XML playlist. You should ensure that the <filename> tag only contains the fienames and not the full URL (or "path"). To check, open the XML playlist in a text editor and ensure that all the <filename> tags only use the filename. Click here to download some simple XML playlist examples.

If you plan on using the embedded playlist option, you will NOT have to upload the audio.mp3 or video.flv files, you'll only have to enter their filenames into the embedded playlist field.