Specify type of source port

[mikew]

While WADPunk points people towards GZDoom, it technically supports any source port: all it's doing is building a command to execute.

I've used GZDoom, Chocolate Doom, and Eternity Engine.

There's a couple of ways of doing this (at least):

Method 1

interface SourcePortType {
  description: string
  iwadFlag: string
  fileFlag?: string
  configFileFlag?: string
  saveDirFlag?: string
}

const gzdoom: SourcePortType = {
  description: "...",
  iwadFlag: "-iwad",
  fileFlag: "-file",
  configFileFlag: "-config",
  saveDirFlag: "-savedir"
}

const eternityEngine: SourcePortType = {
  description: "...",
  iwadFlag: "-iwad",
  fileFlag: "-file",
  configFileFlag: "-config",
  saveDirFlag: "-save"
}

...

Method 2

interface SourcePortType {
  supportsCustomConfig: boolean
  supportsSaveDir: boolean

  buildCommand: (args: {
    executable: string
    iwad: string
    files: string[]
    useCustomConfig: boolean
    gameMetaDir: string
  }): string[]
}

const gzdoom: SourcePortType = {
  supportsCustomConfig: true
  supportsSaveDir: true

  buildCommand(args) {
    const command = [
      args.executable,
      '-iwad', args.iwad,
      '-file', ...files,
      ...(args.useCustomConfig ? ['-config', path.join(args.gameMetaDir, 'config.ini')] : [])
      '-saveDirFlag', path.join(args.gameMetaDir, 'saves')
    ]

    return command
  }
}

What I would like from the chosen approach is:

• To be able to tell the user if the source port allows custom configs
• To be able to tell the user if the source port can keep saves separate
• The ability to list them all to the user
• Pretty adaptable, you never know what args a random source port takes

I like the approach with buildCommand, as that can probably take whatever args are passed to startGame()