[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23134: ------------------------------------- [~mmalina] https://wiki.eclipse.org/Links_and_Buttons This article seems to indicate Buttons are for primary actions or actions with significant consequences. They are more prominent, and draw the user eye more. For examples of buttons, think of Print (significant action), "Save" (significant action), "Show Details" in a progress dialog, which changes the UI significantly by expanding the dialog and adding / showing more widgets. A simple refresh viewer, in my opinion, is very insignificant. I would categorize a simple refresh of a view as a secondary action. It has no significant consequences, and no lasting changes. It does not change the UI by adding or removing widgets in a way that would be confusing to the user without a button. It persists nothing. It is secondary to the table viewer completely. I also personally feel a button would look out of place. And while i disagree with [~mickael_istria]'s link in some respects (website is different than eclipse), it also defends my point: {quote} Actions where users won’t affect the website are where you use a link. These are actions that take users from one page to another without changing anything on the website’s back or front-end. The user is basically a spectator browsing through content. They aren’t doing any actions that require more effort than clicking and viewing. The back-end and front-end of the website remains the same. It’s these situations when you should use a link over a button. {quote} You can argue that I am incorrect here... you could argue that the front end has changed. But it hasn't. The widgets are all in the same places as before. And, as the article says, "The user is basically a spectator [sic] aren't doing any actions that require more effort than clicking and viewing." Hope this clarifies my view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)