Community
Participate
Working Groups
Created attachment 183223 [details] demo1 A user will not always realize that there is a possible improvement in the way he is using Eclipse. It is also extremely difficult for the user to sit and try to analyze what all tasks he does in Eclipse, and is there a better way to do some of those. If a user does something for which there is a better way possible Eclipse should try to notify the user about it. For example, a preference that could be configured, a refactoring that could be used, a quick assist that can be used (or a series of quick assists in some cases). The tips can be shown in a popup on the bottom right of the screen, in a popup near the cursor/mouse pointer, or even using the context help infrastructure. These tips or guidance could be categorized 'new user', 'intermediate', 'experienced user' and a user can choose to see tips from only one selected category. attaching a demo (video) of some examples I quickly implemented (extract with 7zip and view with Windows Media player/VLC) (While this should be done for the entire SDK, I am filing the bug against JDT for now...)
Created attachment 183224 [details] demo2 (some more examples)
Another idea could be to show quick assists automatically, if we can detect in advance what the user is trying to achieve. Something like Bug 328524. Today I came across this preference - Java > Editor > Light bulb for quick assists. Showing a light bulb in the Java editor (other places?) could be another approach. Currently the light bulb is shown too often, e.g. even if only Rename and Assign to local quick assist are available (which is pretty much everywhere in the editor). For starters we should not show the light bulb if only these quick assists are available.
