Community
Participate
Working Groups
As part of defining a Solstice-style Welcome/Intro theme (bug 466370), I found that the stock product logo 'intro-eclipse.png', specified via the introBrandingImage product property, does not fit the Solstice theme style. This logo is included in the Platform, SDK, and EPP products. My approach was to provide an alternative logo (intro-eclipse-bw.png) and change the introBrandingImage property accordingly. But then the other themes look terrible. We need a way for themes to influence how an image is resolved.
https://git.eclipse.org/r/70362 Adds support for resolving theme-specific files via a prefix defined using the 'filePrefix' theme property. When resolving a file path, the Intro first checks for a file with the filePrefix applied to the file component. Adds file prefixes for each of our defined themes. So the Platform and SDK products can now include a 'solstice-intro-eclipse.png' file for a Solstice-specific Eclipse logo.
This change adds a new theme property for Welcome/Intro themes called “filePrefix” used to resolve theme-dependent variants of images that are referenced by the theme. This only affects files specified as product-properties, such as the branding logo. The filePrefix causes the Intro code to first resolve images with the given prefix and then fallback to the path as-is. For example, the Solstice theme defines (simplified; full details in patch): <theme id=“org.eclipse.ui.intro.universal.solstice"> <property name=“filePrefix” value=“solstice-“ /> … </theme> The Platform and SDK products specify their branding logo like: <property name=“introBrandingImage” value=“product:intro-eclipse.png” /> When resolving the introBrandingImage, the code will now first try resolving ’solstice-intro-eclipse.png’ from the product bundle. If not found, it will fallback to ‘intro-eclipse.png’. If a directory is specified (e.g., ‘product:logos/eclipse.png’) then the prefix is applied to the file portion (‘logos/solstice-eclipse.png’). Without this change, product definitions have to explicitly reference a more Solstice-friendly logo. But then the other themes don’t look as intended. [Though to be honest, I think they all look better with the white logo.]
(In reply to Brian de Alwis from comment #2) > [Though to be honest, I think they all look better with the white logo.] No, it did not look good and it also did not fit properly. I currently don't have a Linux box at hand to attach a screenshot.
(In reply to Brian de Alwis from comment #1) > https://git.eclipse.org/r/70362 > > Adds support for resolving theme-specific files via a prefix defined using > the 'filePrefix' theme property. When resolving a file path, the Intro > first checks for a file with the filePrefix applied to the file component. > > Adds file prefixes for each of our defined themes. > > So the Platform and SDK products can now include a > 'solstice-intro-eclipse.png' file for a Solstice-specific Eclipse logo. Please see the discussion on the PMC mailing list.
New Gerrit change created: https://git.eclipse.org/r/71025
Gerrit change https://git.eclipse.org/r/70362 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ua.git/commit/?id=31bcbfb0012425aa1b5b9b9b974cf7ae878f0b79
New Gerrit change created: https://git.eclipse.org/r/71148
I believe these changes resulted in a regression as described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=487713
The return value of UniversalIntroConfigurer#resolveVariable() has changed when a file reference is not found, as identified in bug 487713 comment 11.
New Gerrit change created: https://git.eclipse.org/r/72229
Patrik, would you be able to review the patch at https://git.eclipse.org/r/72229?
Gerrit change https://git.eclipse.org/r/72229 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ua.git/commit/?id=ceb062f8568392a4fc410c9a5bf5faa2fcc5d9fa
Fixed for RC1. Leaving open as still have some doc pending.
(In reply to Brian de Alwis from comment #13) > Fixed for RC1. Leaving open as still have some doc pending. Please open a separate bug for the doc.
Verified in 4.6.0.I20160519-1730.