|Re: [ui-best-practices-working-group] Should editor show new wizard for empty files?|
On 04/20/2017 09:30 AM, Mikaël Barbero wrote:
Definitely the 2nd one.
In this case, it seems like an heuristic of reusing some source folder in the parent hierarchy if existing, or creating a new source folder for the parent project would cover that vast majority of cases. Then, for those who are in trickier state, they'd have to go to JDT project settings (which isn't difficult).
This branch should IMO be avoided: from the file and a source folder, we can infer the package and shouldn't let user configure it in the wizard. The wizard would pre-set the value and not let it be changed. Then if later user wants to change package, they can use a refactoring for that.
Same thing as above. Why letting user change classname if we already know it?
As you present it, it seems more complicated because you focus on the various existing configurations rather than on how to best assist the end-user. I believe the key here isn't to let user do everything from this workflow, but to put constraints and give them a way to do what they most likely want less configuration and less risk of doing something wrong. If they want to do something more complicated, they already have all the necessary workflows to do so,
Back to the top