KVirc attempts to manage scripts in a slightly different way than other clients.
I've tried to join the 'script' and the 'theme' idea all in one.
At the same time I wanted to develop an easy way to create,install and transfer the 'script'.
So here we go:
The 'script' in KVirc is a single file,containing events,popups,aliases,color preferences,
color mappings,the interface options (backgrounds,colors and fonts) and the contents of some directories.
It is easy to transport,easy to create and hopefully portable between different platforms.
All the parts of the scripts are optional ; that means that you can save your aliases but
not save your color mappings...or save the interface options and some background files and
not save your aliases and events....
Setting up the script
Here I assume that you want to save a complete 'script'.
Write your aliases,popups and event handlers.
If your script uses sound files,you should move that files to the
$HOME/kvirc/Scripts/Audio directory.
That files will be shipped with your script.
Set up your mIrc color's preferences.
You can change the entire color palette,but try to be consistent
with the mIrc default colors : for instance,turning the color 0 (white)
in black , may make the other people's text unreadable.
Setup the 'misc options/messages' tab.That options will be stored in the script.
Setup your interface settings
If you're planning to use background images,you should first move the files
that you want to use as backgrounds to the $KVIRCHOME/kvirc/Scripts/Images directory,
and then setup the backgrounds.
In this way you will include the files in your script.
If you want to ship some other files, place it in $KVIRCHOME/kvirc/Scripts/Misc.
Check the $KVIRHOME/kvirc/Scripts/Audio,$KVIRCHOME/kvirc/Scripts/Images and $KVIRCHOME/kvirc/Scripts/Misc for
unused files.Move them in a temp directory or make it invisible so kvirc
will not add them to the 'script' file.
Open the 'save script' dialog , and write a brief description.
Now you can click 'Save'.
This will produce a single file in output.
Notes
-The file that you want to ship should use the 'kvs' exension (scriptname-version.kvs).
-If you're planning to make it available to the public domain, you should ship it in
an archive (something like a tar.gz) , that contains also a README file with a short description.
-If you want to ship other files,remeber to install everything in $KVIRCHOME/kvirc ; don't install
in $KDEDIR/share/apps...and so on.
Index