Should be possible to type in the compile command to execute in the terminal into a text field,
e.g., if compilation is done in a mvn install step.

Even if it was not explicitely closed with a key press.

Can't fix this; the divider just takes a position that is nowhere defined.

Offer possibility to delete corrupt file, etc.

If a parse failure occurs, there is no new info file. Nevertheless, it would be nice to have the same functionality as for the type errors (even more so).

If a module imports a module without rules, its icon will be a white minus on grey ground, even if all rules have the same state. This is irritating.

Due to the complexity of a project and its way to start it in a way that it's debuggable, I would say that a run button is not needed.

If the GUI is open, it caches the configuration read at startup in memory and writes that out if the defaultCompile command changed. If the configuration was changed in the meantime with an external editor, that change is overwritten. I thought the project file is monitored, isn't it?

Still, one more argument for not storing the defaultCompile command in that yaml.

I would go for the following:
If nothing is specified, the initial "default" compile command is either the built-in "compile" script, if it can be found, or the first of the customCompileCommands otherwise. If one is clicked, it is stored in the same location where all other project-related state information is stored.

not to be confused with javadoc comments

Watch Window; enter URI + property and get value

Otherwise you can't see if there were any type problems.

can be done by checking RuleLoc.yml's timestamp with timestamp of .rudi files

Possible ways to fix:
https://github.com/sibvisions/javafx.DndTabPane
https://tomsondev.bestsolution.at/2014/07/28/reorder-and-drag-and-drop-with-javafx-tabpane/

If one of the source files is newer than the compiled output, this should be red, otherwise green.

Extend the signal lamp to provide the following functionality:

• green: compiled and no error/warning
• yellow: compiled, only warnings, right click gives you a menu of warnings to jump to
• orange: compile, with errors (and possibly warnings), right click gives you a menu of errs/warnings to jump to
• red: compile, with fatal error, right click ....
• pink: recompile necessary, left click compiles, right click ...
• hover explains the status

Should enable reconnecting to the server in case of disconnect.

It would be really cool to have a search function in the native editor, preferrably accessible with Ctrl + F

There are, however, no errors shown, so it seems to be just the color marking that is wrong.

@bkiefer

They appear in the yml file as errors of type PARSE_ERROR, but are not shown in the GUI.

Don't add hidden files (starting with '.')

What is now shown in hover should be directly in the menu (the error message in addition to the line number)

Once a special compile command is selected it is very likely that next time you want to use the same command, so it would be very nice if it would 'stick' until something else is selected (and the button accordingly renamed).

change documentation afterwards.