| Re: [epp-dev] Default enablement policy for Code Recommenders in EPP packages |
Yeah, no popups. We should be banning pop-ups across the board. They¹re
super annoying. It would be hard to find a UX expert who would disagree
except for the most critical of messages (like workspace out of memory).
Personally, I¹d like to see a better Welcome page that becomes part of the
users workflow. It would be a great place to bring things like that to the
attention of users.
I guess the other side of that question, why not turn code recommenders on
all the time?
Doug.
On 11/20/2013, 9:56 AM, "Marcel Bruch" <marcel.bruch@xxxxxxxxxxxxxx> wrote:
>Hi package maintainers,
>
>by default Code Recommenders content assist silently disables itself if
>it finds the standard Java or Mylyn content assist being enabled on the
>default tab. On the Eclipse booth at Devoxx last week it turned out that
>many Eclipse users did not know about Code Recommenders being already
>available in their installations because of this silent deactivation.
>
>I¹m now looking for ways how to make Recommenders content assist more
>prominent so that Eclipse users get aware of it. Adding it to the welcome
>page may work but many say it¹s not read very often. I wonder how you¹d
>feel about a popup that (when code completion is triggered the first
>time) informs a user about the engine being available and asking a user
>to enable it or not.
>
>What do you think?
>
>Thanks,
>Marcel
>
>
>
>
>_______________________________________________
>epp-dev mailing list
>epp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev