Bug 80215 - [nls tooling] Provide content assist for NLS strings in Java Editor
Summary: [nls tooling] Provide content assist for NLS strings in Java Editor
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-05 04:45 EST by Brock Janiczak CLA
Modified: 2009-03-31 09:13 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brock Janiczak CLA 2004-12-05 04:45:58 EST
You can currently hover over or ctrl click on an existing NLS string in the java
editor and have it take you to the definition of that string.  It would be
useful to provide content assist when adding them (yes, I am addicted to
ctrl+space).  Currently to get an NLS key you would have to look up the key in
the property file and copy it to the java file (or use the externalize wizard
for new keys).

eg. given the following snippet (assuming content assist is invoked with the
cursor at |)
Messages.getString("key|")
only keys starting with "key" would be proposed.

NLS keys should probably only be suggested when the cursor is inside a string
value ("").

The externalised version (using the current locale) of the key should be
displayed as the info of the assist.  Poposals should be sorted alphabetically.
Comment 1 Dani Megert CLA 2009-03-31 09:13:52 EDT
Note that this now works when using Eclipse's string externalization mechanism.