Gamewide Config Files Would Be a Nice Improvement

[shannona]

It would be nice if instead of the game directories we had simple config files for new games, to make it easier to add ones. I don't know if there are issues requiring JS to have files rather than files with arguments, but absent that, there's not a lot original in each game directory, just a bunch of changes of names and URLs, and that could be done in a config file instead.

[Wyrhtan]

Agreed - the multiple files is an artifact of development, where I needed a single codebase to easily switch between multiple configurations. I'll look into setting up a 'one config file' setup on GitHub.

…

On Sat, Aug 1, 2020 at 1:35 PM Shannon Appelcline ***@***.***> wrote: It would be nice if instead of the game directories we had simple config files for new games, to make it easier to add ones. I don't know if there are issues requiring JS to have files rather than files with arguments, but absent that, there's not a lot original in each game directory, just a bunch of changes of names and URLs, and that could be done in a config file instead. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APUK5525BDZO3JAXKPWH4E3R6ROALANCNFSM4PR6NWAQ> .

-- James Sanders Wyrhtan, Grendel's Revenge GameMaster

[noahgibbs]

I've started setting up DGD a little differently for my work (example: https://github.com/WebOfTrustInfo/prototype_vRWOT). What's going on there is that the app references SkotOS (in that case a fork of it) and then just overrides any files it wants to have different in the "root" directory, which obviously corresponds to "skoot" in traditional SkotOS. And then it serves its own Orchil, game client, Tree of WOE, etc, and it doesn't need copies of any other games' equivalents. It gets orchil.js and similar shared files automatically since SkotOS has a copy of them (or it can reference the Orchil repo, as it will later on.)

I'm using a tool called dgd-manifest in a package called dgd-tools for this, but the basic approach is straightforward and could be done with something like Git submodules as well.

So: that's the approach I've been using to this problem - having apps use other repos, including this one, as libraries. And then they can just have their own app-specific files (e.g. gables.htm, TreeOfWoe.htm, gables.js, gables.css).