Enhancement: new Gradle main project wizard options. (From #241)

[JustGregory-zz]

This is an enhancement request that I originally suggested the basis of, in issue #241 (but decided not to clog up that one with this idea too much).

The basis of the idea is that the new project wizard in this module could be enhanced to permit alternate and/or user-customized build, common, and settings Gradle scripts to be created for a main project, and perhaps some custom build scripts for subprojects as well. I know from some personal development, that the generic Gradle project is somewhat different from a Minecraft-specific Gradle project, and having some templates for the variations might be nice.

But, a lot of my enhancement depends purely on whether you are merely "copying" aforementioned scripts from some other Gradle location. That's fine if you do; I wouldn't force you to stop doing that as a default; but having alternatives is a valuable enhancement idea for me.

To a larger issue. It could be beneficial for your module to provide alternatives for the scripts, perhaps some templates included in the module itself, perhaps in some user-defined location. The wizard dialog could have additional dialog pages: a page for naming subprojects when a main project is being created, and a page for selecting alternative or custom scripts for the main project and subprojects.

For the first dialog suggestion, one enhancement I think would be beneficial is the possibility that I have already decided upon the names of subprojects of a main project. I would like, within the wizard dialog, to be able to specify them, so that automation of creating subprojects along with the main project, is possible. This might take the form of a dialog page with a text-area, where one subproject artifact name is entered on each line of the component, to be parsed and created after the main project is completed.

For the second dialog suggestion, allowing for selecting and applying alternative Gradle scripts in a main and subprojects. This could take the form of a dialog page with a check-box to enable substitution of alternate scripts, and combo-boxes for variations of the build, common, settings, and perhaps even some user-customized scripts. Creating a main project can still occur as normal, but if checkbox from this page is checked AND one of the combo boxes are anything other than "use default", the alternative script(s) can be "copied over" its default target in the main project. This should reduce or eliminate some manual editing of Gradle scripts, if scripts that more closely resemble our intentions are easily selectable. Also, we already have a Preferences panel for this module; we could have a little bit of it for defining custom scripts locations, a "library" of sorts.

I'm sure other commenters could think of alternative adaptations to the above... But I think that all I have typed is a fair balance between benefit to myself as well as others.