Community
Participate
Working Groups
3.3 RC3 In the plugin editor, for any extenion that has a name, the word "name" is underlined to indicate its a link. Clicking on it does nothing. This seems universal, I noticed it with the following extensions: - editors - product - views Nothing in the log
If the name is an externalized string, clicking the hyper link will open the properties file in which it is stored and highlight the value to be substituted. It seems that a better behavior would be to have the "name" label be a link if the value starts with '%', otherwise have it be just a normal label. This is something we can look into post 3.3
RE: Comment #1 Hi Brian, The only problem of implementing your label suggestion is that when you externalize strings and keep the editor open, the hyperlink will not be available (still a label) unless you close and reopen the editor.
Ah, I see what's going on now, thanks. For the non-externalized case, either 1. Remove the link as suggested, or 2. Provide some feedback when clicking on it (e.g. "No corresponding externalized String"), or 3. Deluxe would a wizard that helped you author the string externalized :)
tagging bugday
The last solution proposed by Kevin can be implemented using the PDE GetNonExternalizedStringsAction in the classTranslationHyperlink responsible to open associated .properties file. Am i right ? We can create a private method called each time before false is returned in the openHyperLink() method and do this in our private method : // Cretaes a new Externalize Action // May be there is one way to get an already created and prepared action ?? GetNonExternalizedStringsAction action = new GetNonExternalizedStringsAction(); // Set the selection within the action with current selection action.selectionChanged(null, PDEPlugin.getActivePage().getSelection()); // Run the action with null, null works here but may be dangerous ?? // How could i do better ? action.run(null); Thanks Manu http://manuelselva.wordpress.com
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
