Issue 3 in constants-to-enum-eclipse-plugin: Refactoring menu entry

[codesite...@google.com]

Updates:
Status: Fixed

Comment #6 on issue 3 by b.muskalla: Refactoring menu entry
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=3

Added menu item to all refactoring popup menus (eg, Package Explorer,
Outline), added
item to main Refactoring menu

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #7 on issue 3 by raffi.t.khatchadourian: Refactoring menu entry
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=3

Thanks! Obviously, I haven't yet taken a look at this, but what happens
when the refactoring is selected on, for
example, a class? Are all fields from the class extracted and sent as input
to the refactoring? Also, does right
clicking a field in the editor show an option for the refactoring? Thanks
again!

[codesite...@google.com]

Comment #8 on issue 3 by b.muskalla: Refactoring menu entry
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=3

Currently the refactoring is only active if you selection is a field.
We could think about adding classes as valid selection and take all the
class fields
into account. Would you open a bug for that?

Regarding the text selection: That's currently not yet possible as it
requires a little
more work in the handler activeWhen strategy. I opened issue 13 for this.

[codesite...@google.com]

Comment #9 on issue 3 by raffi.t.khatchadourian: Refactoring menu entry
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=3

Ah, sorry, I got confused with another issue. There is an open issue for
this, its issue 4.