by Kaucukovnik » Tue Jan 22, 2019 5:48 am
Glad you like them, and yeah, hoped master Yoda would produce a chuckle.
I use heavily gutted UGUI for the launcher, it turns a html page into a desktop program that can assemble console commands from radio buttons selection and execute them. The downside is that adding or removing stuff is fairly complex, which is kind of a problem for launcher platform. Still good enough to organize my personal collection if nothing else comes along.
So far it looks like this:
http://www.mediafire.com/view/frs9z0hne ... r.jpg/file
I have only a bit of each category working, just as a proof of concept. As I said, adding content is tedious, things must be defined at multiple places in the file. I'd hate to go through the chore, present the result, and then see someone go "let me show how it's done" and whip up a nice real launcher program with easy setup. So I'm testing the waters first.
Here is my idea of a pretty, easy to use launcher:
Spoiler:
Directories for different categories:
DATA_MOD: vanilla Doom + gameplay mods that are compatible with custom maps and megawads
DATA_WAD: maps and megawads
DATA_WAD_ID: place for official wads, displayed on top of wad list
DATA_MUSIC: music replaceres
DATA_HUD: user interface mods
DATA_MISC: various additional gameplay mods that can be combined with others, unlike other categories multiple entries ca be selected
Additional content would be placed in subdirectories. If a config file is created in the subdirectory, settings from it will be used. Otherwise default values will be assumed. If no applicable (wad, pk3) files are found in a directory, it is ignored.
Config file values:
NAME: if not defined, directory name is used
DESCRIPTION: if not defined, textbox is just left empty
ICON: if not specified, the first ico/png file in the directory will be used, if none found, default graphic for the category will be used
PREVIEW: if not specified, the first jpg image in the directory will be used, if none found, description box fills the space
GZD_VER: gzdoom version, if not specified the latest installed version will be used*
LOADFILES: if not specified, all applicable files from the subdir will be loaded (wad, pk3...)
INCOMPAT: specified by filenames, if none listed, the launcher will allow this piece of content with every other in the selection
WARP: if specified, the launcher also gives difficulty choice, for wads that replace later levels and can't be started right off the bat from the game menu
OPTIONS section: (when a mod has optional components, tickboxes appear in the description box)
OPTION NAME: file(s)
COMPATIBILITY section:
file name of the other mod: compatibility fix file(s) - when a mod with available fix is detected, patch file(s) get loaded too
So if you have a simple to install piece of content, you can just create a directory and dump all the files in it.
I already have a bunch of icons with Doom artwork to use when in need for an icon.
* multiple gzdoom versions in separate subdirs, all sharing one config file so that your personal setting work across everything. I'm currently doing this via batch files, and it's a great way to combine content old and new in a single mega-installation.
Glad you like them, and yeah, hoped master Yoda would produce a chuckle. :)
I use heavily gutted UGUI for the launcher, it turns a html page into a desktop program that can assemble console commands from radio buttons selection and execute them. The downside is that adding or removing stuff is fairly complex, which is kind of a problem for launcher platform. Still good enough to organize my personal collection if nothing else comes along.
So far it looks like this:
http://www.mediafire.com/view/frs9z0hnenctb83/launcher.jpg/file
I have only a bit of each category working, just as a proof of concept. As I said, adding content is tedious, things must be defined at multiple places in the file. I'd hate to go through the chore, present the result, and then see someone go "let me show how it's done" and whip up a nice real launcher program with easy setup. So I'm testing the waters first.
Here is my idea of a pretty, easy to use launcher:
[spoiler]Directories for different categories:
DATA_MOD: vanilla Doom + gameplay mods that are compatible with custom maps and megawads
DATA_WAD: maps and megawads
DATA_WAD_ID: place for official wads, displayed on top of wad list
DATA_MUSIC: music replaceres
DATA_HUD: user interface mods
DATA_MISC: various additional gameplay mods that can be combined with others, unlike other categories multiple entries ca be selected
Additional content would be placed in subdirectories. If a config file is created in the subdirectory, settings from it will be used. Otherwise default values will be assumed. If no applicable (wad, pk3) files are found in a directory, it is ignored.
Config file values:
NAME: if not defined, directory name is used
DESCRIPTION: if not defined, textbox is just left empty
ICON: if not specified, the first ico/png file in the directory will be used, if none found, default graphic for the category will be used
PREVIEW: if not specified, the first jpg image in the directory will be used, if none found, description box fills the space
GZD_VER: gzdoom version, if not specified the latest installed version will be used*
LOADFILES: if not specified, all applicable files from the subdir will be loaded (wad, pk3...)
INCOMPAT: specified by filenames, if none listed, the launcher will allow this piece of content with every other in the selection
WARP: if specified, the launcher also gives difficulty choice, for wads that replace later levels and can't be started right off the bat from the game menu
OPTIONS section: (when a mod has optional components, tickboxes appear in the description box)
OPTION NAME: file(s)
COMPATIBILITY section:
file name of the other mod: compatibility fix file(s) - when a mod with available fix is detected, patch file(s) get loaded too
So if you have a simple to install piece of content, you can just create a directory and dump all the files in it.
I already have a bunch of icons with Doom artwork to use when in need for an icon.
* multiple gzdoom versions in separate subdirs, all sharing one config file so that your personal setting work across everything. I'm currently doing this via batch files, and it's a great way to combine content old and new in a single mega-installation.[/spoiler]