Community
Participate
Working Groups
Provide a way to run the String Externalization on a smaller context. I would prefer it to be possible to select a portion in Java file and run the String Externalization on only the selection. If no selection is made, the wizard can continue to run as it does now. The selected context can be shown in the context section of the wizard.
What's the use case for this?
It gets bit difficult when one has to externalize or internalize the strings for one method and the whole class contains lot of strings. Such a feature comes handy when you are writing a new class and do not wish to touch the unfinished portions yet.
(In reply to comment #2) > It gets bit difficult when one has to externalize or internalize the strings > for one method and the whole class contains lot of strings. Either the product and hence your whole class is externalized or it fails regarding this. I don't think it's smart to encourage people to only partially externalize their code. Either externalize everything at the point when you touch it or do it when finished with the whole class. What's the befit of externalizing parts of an unfinished class given you have to visit the class again later to complete the externalization?
My argument is not based on best practice for string externalization. My problem is very elementary. I have a unfinished class and I want to do some internalization (why? well say I copied it from some where and want to modify it). Currently, its almost impossible to achieve this using the wizard. It does not show the strings in any order (say order of appearance). Can not even sort the table. Context section is not of much use when the class has lots of such Strings as it can only show a small snippet only. My request is to help automate a small trivial mundane task.
See also Bug 183334 for the string internalization case. At times even I have wanted to internalize a 'few strings', when I want to copy/move some code.
If you decide to provide a way to internalize, please keep a way which does not delete the keys. When the keys are used in other Java files, they throw compiler errors all over the place.
(In reply to comment #6) > If you decide to provide a way to internalize, please keep a way which does > not delete the keys. When the keys are used in other Java files, they throw > compiler errors all over the place. Interalize can already be done. This request is to scope the wizard to the selection. And of course it should not delete the key if it's still used. If that's the case then please file a separate bug report.
