Bug 428619 - [nls tooling] Show translation value of property on mouseHover for new message extension
Summary: [nls tooling] Show translation value of property on mouseHover for new messag...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-20 04:46 EST by Dirk Fauth CLA
Modified: 2014-02-21 04:33 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Fauth CLA 2014-02-20 04:46:28 EST
If you hover over a member of a NLS based class in a class that uses the member, the value for the current active Locale will be shown as tooltip in the editor.

This hover mechanism should be extended to also support the new message extension that is introduced with Eclipse 4.4.

See http://blog.vogella.com/2013/05/22/eclipse-internationalization-part-24-new-message-extension-by-dirk-fauth-and-tom-schindl/ for some informations on the new message extension.
Comment 1 Stephan Herrmann CLA 2014-02-20 16:57:55 EST
NLSStringHover is owned by JDT/UI
Comment 2 Dani Megert CLA 2014-02-21 04:25:12 EST
We won't have time for this during 4.4. It will not be enough to just look at the reported case. The whole NLS tooling in JDT would have to be revisited and adjusted.
Comment 3 Dirk Fauth CLA 2014-02-21 04:33:26 EST
(In reply to Dani Megert from comment #2)
> We won't have time for this during 4.4. It will not be enough to just look
> at the reported case. The whole NLS tooling in JDT would have to be
> revisited and adjusted.

I expected that answer. :)

The tickets I created for the missing parts of the internationalization stuff (wizard, hover, translation registry) are thought for Luna +1, as they can't be implemented and tested well for the Luna release. But I created them now so:
a) the missing parts for a clean internationalization implementation are documented
b) maybe others than me might want to take a look at it
c) it could be something for GSoC or a hackathon