Improvements to Build Dialog

[indolering]

There are a lot of problems with the build dialog ("File->Project Settings->Modules") and I thought it might be better to create a checklist instead of spawning 6 low-priority tickets.

• [ ] Hide "Target" drop down in irrelevant tabs (such as when using .hxml file).
• [ ] Auto suggest/create intelligent default for output file name + extension.
• [ ] Make requirement for specifying output file name visible in UI and/or throw error when run.
• [ ] Support multiple targets per module under Haxe Compiler option.
• [ ] Add "Other" option that supports arbitrary commands (i.e. make).
• [ ] Support running external tools before and after build.
• [ ] Push flash application debugging setting to a new tab.

[EBatTiVo]

@indolering

I assume you mean the "File->Project Settings->Modules" dialog when you use the term "build dialog."

Please describe what you mean for the item "Support multiple targets per module." (e.g. Compile for .java and .cpp; or Compile some files to one output, and other files in the same module to a different output; or Compile using HXML and NME; or something else).

Do you propose using arbitrary commands instead of those derived from the "Compile with:" radio buttons? (That seems to be what you mean by "Specifiy arbitrary executable commands.")

[indolering]

Please describe what you mean for the item "Support multiple targets per module."

The Haxe Compiler option should consist of default settings for all targets (executable name, output directory, main class, parameters) and a list that users can populate with different targets (JS, PHP, CPP, etc). Each target should allow the user to specify additional parameters and override the defaults (executable file name, parent directory name, output directory path, the main class, and an option to ignore the default parameters).

So, for example, if I want to produce a library for PHP, Node.js, and the browser; I should be able to configure a PHP target with the default settings, a JS target with a parent directory named "node", and a final JS target with a parent named "browser."

I'm ignorant of how NMML and OpenFL work, I assume that they are similar to HXML and allow for multiple targets.

Do you propose using arbitrary commands instead of those derived from the "Compile with:" radio buttons? (That seems to be what you mean by "Specifiy arbitrary executable commands.")

Right, so add an "other" option and clone the "external tools" screen:

Adding direct support for Make might be a good idea: compiling a library into multiple languages and then pushing to different package management systems requires something that can execute arbitrary commands. HXML isn't flexible enough and you don't want a project to become dependent on the IDE to build the project.

[indolering]

Note that I added "Push flash application debugging setting to a new tab." to the list : )

[indolering]

@EBatTiVo My apologies if I came off as demanding or ungrateful, I'm a UX guy so I figured you just needed some specs to build against. Feel free to edit the list down :p