Contact information


www.firework-screensaver.com   Flaredance Firework Screensaver official site
www.firework-screensaver.com/support/ Flaredance Firework Screensaver support
www.firework-screensaver.com/order/ Flaredance Screensaver online order form
www.firework-screensaver/download/ Flaredance Screensaver updates and fireworks
   
support@firework-screensaver.com General support questions and suggestions
sales@firework-screensaver.com Ordering and registration questions
press@firework-screensaver.com Public relations and press related questions

Information for resellers

If you have ability, opportunity and want to became our reseller, please, look www.firework-screensaver.com/reseller/ for available affiliate programs, offers, promotional materials and additional information.

Version history

Current version 1.10 (15 February 2006)

  • motion blur;
  • particle glowing halo;
  • new firework types;
  • date/time showing;
  • minor performance tweaks and fixes.

Version 1.00 (21 November 2005) was the first public release

Making your own fireworks

Flaredance Firework Screensaver is flexible enough to allow you construct the fireworks at your own! All you need for this is to make firework configuration file, name it as "particle_***.xml" and place it to the Flaredance Firework Screensaver folder.

Firework configuration XML file format

Empty file looks like the following:

<?xml version="1.0" encoding="windows-1252"?>
<particles xmlns="http://www.zerge.com/particles.xsd">
</particles>

Inside the tags pair <particles></particles> can be several <Particle> tags:

<Particle
   name="unique particle configuration name"
   launch="set to 1 to allow launching this"
   trailsound="sound to be played while particle flies"
   deathsound="sound to be played when particle dies"
   inherit="another configuration name to inherit parameters from">

   <description>short description text</description>
   <lifetime value="particle life time in seconds" randomness=""/>
   <density value="particle density in kg's per m3" randomness=""/>
   <energy value="fuel energy amount per kg" randomness=""/>
   <colorhue value="particle color hue" randomness=""/>
   <colorsat value="particle color saturation" randomness=""/>
   <smoke value="smoke intensity 0..1" randomness=""/>
   <spread value="trail particle spreading energy" randomness=""/>
   <mass>
     <carried value="mass (kg) of carried particles" randomness=""/>
     <trail value="mass (kg) of trailing particles" randomness=""/>
     <fuel value="mass (kg) of fuel" randomness=""/>
     <light value="mass (kg) of light fuel" randomness=""/>
     <explosive value="mass (kg) of explosive" randomness=""/>
   </mass>
   <intensity>
     <trail value="trail particles expense kg/sec" randomness=""/>
     <fuel value="fuel expense kg/sec" randomness=""/>
     <light value="light expense kg/sec" randomness=""/>
   </intensity>
   <timing>
     <trail invert="">
       <delay value="" randomness=""/>
       <hold value="" randomness=""/>
       <pause value="" randomness=""/>
     </trail>
     <fuel invert="">
       <delay value="" randomness=""/>
       <hold value="" randomness=""/>
       <pause value="" randomness=""/>
     </fuel>
     <light invert="">
       <delay value="" randomness=""/>
       <hold value="" randomness=""/>
       <pause value="" randomness=""/>
     </light>
   </timing>
   <trails>
     <trail value="name of trail particle" weight=""/>
   </trails>
   <childs>
     <child value="name of child particle" weight=""/>
   </childs>
</Particle>

Remarks

Sound parameters can be either built-in sounds ("none", "start", "flight", "death" or "clap") or external PCM waveform audio files. In last case, sound parameter value is an absolute file path to *.wav file or file path relative to a folder where configuration file resides.

Randomness parameter is a floating point value from 0.0 (determined) to 1.0 (random). For example, if you set value to 5 and randomness to 0.5, during simulation this parameter will vary from 2.5 to 7.5, i.e. at ±50% of base value.

Color saturation varies from 0.0 (grayscale) to 1.0 (full-color). Color hue value varies in same range, where 0.0 corresponds to blue, 0.3 to red, 0.5 to yellow, 0.7 to green, 0.9 to cyan and 1.0 blue again.

Carried particles are particles to be released after explosion. Trailing particles are being thrown during flight.

Fuel used to give additional energy to the particle.

Timing parameters are used to set the mode of expending fuel, trails and light emission. Timing parameter has delay, hold and pause randomizable values measured in seconds.
Delay determines initial time of inactivity.
Hold determines length of active part of pulse.
Pause determines length of inactive part of pulse.
Hold and pause times change each other while particle is active and corresponding resource (fuel or light emitter) was not depleted.

Timing can be inverted by setting 'invert' attribute to non-empty value.

Intensity parameters determines amount of resources expended per each second of activity.

List of child or trail particles can contain several kinds of particles. Circular dependencies are not allowed. You can adjust ratios between several particles in children or trails lists by setting different 'weight' attributes to them. These weights will be normalized before operation.

Using inheritance adds flexibility to configuration. You can create essential kinds of particle configurations and then simply inherit them by changing only colors, for example.

Sample configuration can be found in the Flaredance Firework Screensaver folder. This file named as particle_example.xml.

Localization

You may help us to translate user interface and online help file. The reward for it will be a free full copy of the Flaredance Firework Screensaver. It is included into the Flaredance Screensaver text package noted below.

User interface

Translating this product is quite easy. First of all, you must translate the language file with the interface elements. It is named "english_locale.xml".

Partially, the locale file is shown below. Translate and change only red-marked items. Name a new file accordingly to the translation language. Note, that language name must be written on English.

<?xml version="1.0" encoding="windows-1252" ?>
<LOCALE language="English" helpfile="Flaredance Screensaver Help (English).chm">
...
<PAIR key="@00101">Camera</PAIR>
<PAIR key="@00102">Fly around</PAIR>
<PAIR key="@00103">Fly through</PAIR>
...

Online help

Another file that must be translated is "Flaredance Screensaver Help (English).chm" which can be found in screensaver directory. It contains online and context help. This file is compressed html code, so it will not be so easy to decompile it. We packaged all text information which needs to be translated into single zip-archive file.
You will find it at www.firework-screensaver.com/flaredance_text.zip.

Contents of the flaredance_text.zip file:

README.TXT Short information about the Screensaver.
LICENSE.TXT End user license agreement.
ENGLISH_LOCALE.XML User interface language file.
CSHELP.TXT Context help topics file.
XXX.HTM Help topic files.

After translating these files, pack them back into archive and send it to support@firework-screensaver.com. We will do the rest to make a final language package. After we publish it, you will be able to review it. After publishing the package, you will be rewarded with a free registration code.