Community
Participate
Working Groups
Provide a separate properties file editor, and enhance the Java editor to display the value of and navigate from an NLS key in code and the corresponding entry in the properties file. [JDT Text]
It would be good to have a tooltip that displays the value of an externalized string when hovering over the property key in the Java Editor (maybe that is already in the works). Currently that tooltip displays the type info of the current type if the externalize strings refactoring wizard finished with the initial resource key prefix suggestion left unchanged. (this was added as 81750 initially which could be marked as duplicate)
Checkout 3.1 M4: besides feature 81750 it also contains: - navigate from Java Editor to Properties file Ctrl + Mouse-click - syntax coloring for properties files - spell checking in Properties file editor - navigation from key in Properties file to its references via Open (F3) and Ctrl + Mouse-click
Thanks first for the great enhancements! But I have one trouble and one enhancement proposal: First the enhancement proposal (use of multiple message resource files): Another checkbox: 'Filter all from other accessor class' Which should filter all those entries from accessor classes different from the one currently specified in drop-down 'Accessor class': (at the moment they give a trouble marker ('Entry is missing in properties file')) This is needed for working with multiple message files, as else the wizard always gets cluttered by the trouble markers. Bug zoo: I didn't check out from CVS, but for a (fresh) 3.1 M4 build: >> Checkout 3.1 M4: besides feature 81750 it also contains: >> - navigate from Java Editor to Properties file Ctrl + Mouse-click Doesn't work. Tried on key string ("FooClass.key"), marker (//$NON-NLS-1$). Nothing happens there. For Message class and method usual Java navigation works (as it should). >> - syntax coloring for properties files >> - spell checking in Properties file editor >> - navigation from key in Properties file to its references via Open (F3) and >> Ctrl + Mouse-click thanks, thanks, thanks :)
Axel, please file a bug report for the bug with steps to reproduce and a feature request for the feature. If we decide to implement your feature we can link it to this plan item.
The Eclipse style of externalizing strings into a static string fields (introduced with 3.1M6) is a great, long awaited enhancement. But for the moment it lacks the value lookup provided by a hover. I thought of a solution that adds the value as javadoc to the static fields but that is not as consistent as it is now with the bundle-based lookup. But maybe the NLSHintHelper could be enhanced to also look for references to static fields within types with a resource bundle.
The tooling for the "standard" NLS approach was already done once the new style was introduce. There was not enough time to provide the same tooling for it. We only adapted the Externalize Strings wizard. For 3.2 the following will have to be done for the new approach: - Eclipse NLS Search - Eclipse NLS hover - Eclipse NLS hyperlinking
see also bug 91500.
.
