[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] Should editor show new wizard for empty files?

I think it would be useful to analyse proposals from different categories of our users. For newcomers, a wizard could be very helpful. But it also risks becoming like Clippy for advanced users. 

Stepping back, I do remember the confusion from some newcomers to JDT and PDE on how to create a new class. They expected to just open a new file and start coding, and then manage where they should put it after the fact. The concept of source containers was particularly confusing (and it confused me for a long time too). Once explained, they got it.

(Off topic but perhaps JDT should hide the source containers except for projects with multiple source containers.)

I sometimes wonder if we wouldn't benefit from providing a "tour" for first time users. Or opening a tour when starting previously unseen functionality.


> On Apr 21, 2017, at 7:01 AM, Torkild U. Resheim <torkildr@xxxxxxxxx> wrote:
> I would have to agree with Dani here â popping up a wizard when I open any empty file would be a huge annoyance. Showing the wizard when creating the file would be less so.
> Best regards,
> Torkild
>>> 21. apr. 2017 kl. 11.14 skrev Daniel Megert <daniel_megert@xxxxxxxxxx>:
>>> Would you be so kind to elaborate why? do you think that shwoing a wizard for empty files would lead to a worse user-experience or to some technical drawbacks?
>> Because the file is already there. Invoking a wizard or some other smartness when I open the file is just bad practice.
>> Dani
> _______________________________________________
> ui-best-practices-working-group mailing list
> ui-best-practices-working-group@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group