jwocky/jh-launcher

jh-launcher's Issues

Callsign selection from Launcher

Create the ability of select a callsign from the launcher before launching,

This includes either taking codes from JAFVA or not using JAFVA to indicate a launching callsign

Obtain STDout and STDerr from FGFS

Selecting Aircraft directory

I had already ask about this, but I want to propose again,

To select an Aircraft directory, not use One aircraft to select the directory, but instead the parent.

Example

/myhome/myaircrafts/theLineage

Selecting /myhome/myaircrafts should suffice, as many aircrafts could reside in this directory

(similar applies to selecting terrain packages)

Terrain Alternatives

Currently it is very obvious how to add Terrain packages (terraGIT or others packages), but it is not obvious how to launch with terrasync. This would be a good addition as many users can't or won't use terraGIT (not know howto, don't want, not suficient disc, etc)

FG generic protocol needs to be in FGDATA

Verify if this can be corrected

Configuration File

A few recommendations about JHLConfig.xml

1. Create a template. If the file is template, open the launcher in an empty Settings place so user can create his own settings (instead of inheriting Jwockys while making Jwocky's settings public)

2. Make the JHLConfig.xml file not trackeable by git, so regardless of user, the source code appears only to always have the empty template

3. If the JHLConfig is an empty template the java JHL opens on an empty tree of Settings page

4. Make the JHL able to SAVE the Settings in the Config file

5. Make the JHL reading the Config File (if not empty template) at launch, as it currently overwrites the whole Config content to JWocky's configuration when program is launched

Multiplayer from Launcher

Add the ability of the user to configure multiplayer servers from the launcher

Add a license

Indicate what license covers this software