Dominions Skin browser

[Leif_-]

Version 0.2 is now up, same location, and it now supports zipped themes and command-line arguments.

Zipped themes must be named on the pattern of SkinName.skin.zip and located in the dominions3/skins directory. The zip file must not contain more than one directory. I've put up an zipped theme as an example.

The command-line parameters are:

--skin Name Activates the named skin without opening a GUI
--directory Dir Sets the Dominions 3 directory. Note that "Dir" has to be specified with forward slashes and not the usual backslashes used by Windows.
--run Automatically starts Dominions 3
--dom3args Arguments Uses the specified arguments to start Dominions 3

So, putting it all together:
Code:

---

java -jar DominionsSkinBrowser.jar --dir C:/Game/Dominions3 --skin Jungle_Nights --run --dom3args "-w -a -f -s"

---

The above command will start Dominions 3 in a window, with no animated backgrounds, fade effects or sound, with the skin "Jungle_Nights."

[Leif_-]

Gandalf Parker said:
Glad to see you back Leif. Id love to see some of your Dom2 stuff regenerated.

Oh, I haven't been away as such. Just quiet. What particular stuff did you have in mind? The random map themes thing (.ran files) has been updated to Dominions 3 already. The random mod script should work pretty much as is, but it'll need updating with the new unit abilitites.

[Leif_-]

So, latest upgrade to the SkinsBrowser program is a connection to an online repository of skins. The repository is pretty sparse at the moment (only three skins there yet,) but when I get a free moment I'll try to add to it. I know there were some skins posted to the forums a while ago, so I'll do some thrawling.

The program can be found here, and the source-code here.

A screenshot of the program is located here.

Further, the contents of the README.txt:


== Dominions Skins Browser ==

The DominionsSkinsBrowser is a small utility for browsing, downlading
and activating graphical skins for the Illwinter game Dominions 3.


== Prerequisits ==

You need a Java runtime environment for Java 1.4 or later installed on
your computer.

(It can also be a good idea to have Dominions 3 installed, as the
program is pretty pointless otherwise.)

== Installation instructions, Windows ==

Unzip the file DominionsSkinBrowser.zip wherever you want to have
it. The resulting directory DominionsSkinBrowser contains a java jar
file, DominionsSkinBrowser.jar. To run the program, double-click on
this jar file.

Tip: By creating a shortcut to the DominionsSkinsBrowser.jar and
append command-line arguments in the Target field you can create easy
short-cuts to start Dominions with a specific skin:

Right click on the DominionsSkinBrowser.jar file and select "Create
shortcut here".

Next, right click on the created shortcut. In the field Target, after
the rightmost quotation mark, append the command-line arguments you
want, for instance "--skin Shiny_Lava --run" (without the quotation
marks.) This will activate the skin "Shiny_Lava" (if it is available
locally) and start dominions.

Rename the shortcut and give it a descriptive name, for instance
"dom3lava"



== Installation instructions, Linux ==

Unzip the file DominionsSkinBrowser.zip wherever. This creates a
directory DominionsSkinBrowser. Inside you'll find a jar file. To run
the program from the command-line, execute the jar file by the command
"java -jar DominionsSkinBrowser.jar"

Options to the program can be added after the name of the jar-file,
such as: "java -jar DominionsSkinBrowser.jar --skin Shiny_Lava --run"


Tip: Use alias commands in your .bash_profile to set up short-cuts to
starting Dominions with particular skins:

"alias dom3lava java -jar DominionsSkinBrowser.jar --skin Shiny_Lava
--run"


== Useage ==

The first time the program is run, it will try to locate where
Dominions 3 is installed on your system. If it can find this directory
it will create a skins/ subdirectory for storing your skins. Next, it
will create a backup of the default skin and store it in
skins/Illwinter_Default.

The program's GUI will then appear. On the left side you have two
lists, one containing your locally installed skins (the first time the
program is run this will only contain the backup it just made,
Illwinter_Default) and, barring any network errors, one containing the
skins available from the repository.

Selecting a skin, wheter locally or in the repository, will pop up a
skin info box on the right side. This box contains the name,
description and author of the skin, as well as any screenshots that
belong to the skin.

Also on the left side is a field for entering the dominions 3
directory if the program couldn't find it automatically (press
"browse" if you don't want to type in the location.) Just enter the
directory path and press enter.

Local skins can be activated (copied into the Dominions3 directory to
be used by the Dominions 3 program the next time its started), and
skins in the repository can be downloaded into your local skins/
directory. Use the "Activate" and "Download" buttons respectively.


== Command line arguments ==

The program takes the following optional arguments:

--directory DIR_NAME
uses DIR_NAME as the dominions 3 directory. Handy if you have
Dominions installed in a location where the SkinsBrowser won't
find it automatically.

--skin SKIN_NAME
Activates the named skin without opening the GUI.

--run
Starts Dominions 3 (use with --skin to start Dominions 3 with
a specific skin)


== TO DO ==

Allow input of the repository location (no hardcoded address.)

Cache BufferedImages to shorten the time it takes to display a
repository skin.

Add uploading of local skins into the repository.

Add repository support for maps and mods as well as skins.


== Locations ==

The canonical location for this program is at
http://dominions.dimnakorr.com/programs/skinsbrowser/

The source-code (which is released into the public domain) can also be
found there.

== Questions, comments? ==

Direct them to leif dot roar at dimnakorr dot com, or post
them on Shrapnel's Dominions forums.

[Gandalf Parker]

Great program.
And even greater instructions Good docs are so often lacking in good programs