Bugzilla – Full Text Bug Listing
| Summary: | [GlobalActions] Refresh button on Project menu | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Eugene M. Steinbacher <gsteinbacher> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | alex, nikolaymetchev, remy.suen, simon_arsenault |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Eugene M. Steinbacher
The Refresh action is already provided in File>Refresh and the navigator and packages explorere have bound the action to F5, so it is easily accessible. Moving to platform UI for comment/disposal. There is still no way to refresh the project without highlighting the project name. I would like to be able to refresh the project without having to go to the scroll to the top of the Package Explorer/Navigator screens. I know this seems a bit picky but when the project gets refreshed a hundred times a day it becomes a "nuisance" to not have a "one key away" approach. Maybe I am missing something....is there another way to compile only the dirty source files? If multiple source files in a project are changed outside Eclipse then yes, refreshing the project is the easiest way to do a build. If the files are changed inside Eclipse you don't have to do a refresh. We use code generators to automatically generate code for us. We usually run these a dozen or more times a day. Everytime this is done we have to refresh the project. Sure would be nice to be able to do this without having to scroll to the top of the Package Explorer view each time. It's definitely a low priority item to work on, but it would be a nice feature for me. Eugene, would you be interested in contributing code for this? We could not call the action "Refresh" as it would confused the user (File > Refresh and Project > Refresh). But maybe if it was called Project > Refresh All? Please annotate this bug report if you are interested and when you would expect to have code ready for us to review. this menu option can also be added as a button on the toolbar much like the internet explorer refresh button. It should be named "Project: Refresh Project". That keeps it clear and unambiguous. "Refresh All" would indicate refreshing all files in all projects (just like "Rebuild All" means rebuild all projects). It should be enabled when you are in an *editor* for a file under than project, not just when the project is selected in the navigator. If an editor is enabled, "File: Refresh" should only apply to that file. (In fact, to be clear, if you are editing file foo.txt, the File menu item should be renamed "Refresh foo.txt"). Because of this mode, the comment "The Refresh action is already provided in File>Refresh" is not true. "File:Refresh" and "Project:Refresh Project" are technically different actions, although sometimes they would have the same target. As for F5, there should always be a menu item corresponding to a keyboard shortcut, so that people can *find* the command if they haven't already memorized how to do it. (And it goes without saying that the menu should display the F5 hotkey, so once you find it, you can memorize it.) Do the new workspace preferences for refresh automatically solve this problem sufficiently? Assigning to component owner PW These will not be worked on. Please re-open if you feel the community should get a crack at them. |