As I understand, this PR changes the current New Project behavior to:
1. Introduce a new popup so that the user chooses the base path before naming the project or choosing a project file name. 2. Automatically fill in the project name and filename based on the project folder.
What I dislike about this new method.
* Adds new popups (folder selection). * Increases the number of steps for users who do not want the defaults. * *Requires* users to select the project base path first. What about users who prefer to name the project first or select a filename first? + There are legitimate cases where the base path aren't known at time of project creation. (example below) * *Still* confusing for users who (are completely new to projects and) don't know the purpose of selecting the folder. + Most people do not stay new users forever. Experienced users should be allowed to streamline their workflow. This PR *prevents* that.
My workflow has been:
1. Choose a filename for the project first. 2. Then change the name. 3. Change the base path last. Sometimes I leave it alone and change it from Project Preferences later because the project folder may not yet exist at the time of project creation. For instance, I may not have cloned from git yet. 4. Update build commands *and* paths. (I sometimes defer choosing base path to the Project Preferences dialog because build commands and paths cannot be changed from the new project dialog.)
So this PR is *not* "compatible with [all] existing user's workflow*".