| Summary: | org.eclipse.jface has icons in package folders | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Lars.Vogel, psuzzi, tom.schindl |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Markus Keller
Also check that the icons are accessed via ImageDescriptor#createFromURL(URL) and HiDPI variants are used if available (bug 382972). (In reply to Markus Keller from comment #0) > org.eclipse.jface has icons in package folders. That's wrong. The icons must > be moved into the correct icons/full/... folders and references must be > fixed. Great to hear, this annoyed me also in the past. I'm not an expert in plain Java-Apps but if you run outside OSGi (and JFace is implemented this way), would that cause a possible regressions if other libraries also keep there icons in "icons/...." package?
Suppose the following
Today:
mylib.jar
+ icons
+ full
- help.png
jface.jar
+ org
+ eclipse
+ ....
+ icons
+ full
- help.png
Proposed change:
mylib.jar
+ icons
+ full
- help.png
jface.jar
+ icons
+ full
- help.png
JFace already has an /icons/full/ folder that contains images (even some duplicates), so this would not be something new. Loading the scattered icons directly has also caused translation problems in the past, see e.g. bug 176993. On a flat classpath, I guess there is a chance for conflicts, but that's IMO acceptable for people who choose to run that way. We should do the cleanup early in 4.7, so that we have enough time to react if anybody has a real problem with it. 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. -- The automated Eclipse Genie. |