My Opera
Relationship between the standard skin and custom skins
Tuesday, January 18, 2011 5:28:59 PM
In my blog post Getting started with skin editing I describe how to extract the standard_skin.zip to get started. While this is how I work on Operas standard skin, it is not how you should be working.
In the above graphic you can see the relationship between the standard skin and custom skins (which is also how the OS X skin is applied). The standard skin provides a base that the custom skin can fall back to. If a skin section is missing in the custom skin, it will use the corresponding section from the standard skin.
This means that if you customize a specific feature, for instance speed dials, you can add only your overrides to the skin, and leave the rest blank. The advantage of this approach is that we can update the standard skin and your skin will continue to work, unless we change the code underneath.
TL;DR
Do not use the standard_skin.zip as a base for your custom skin, instead create a minimal skin with only the changes you want.
In the above graphic you can see the relationship between the standard skin and custom skins (which is also how the OS X skin is applied). The standard skin provides a base that the custom skin can fall back to. If a skin section is missing in the custom skin, it will use the corresponding section from the standard skin.
This means that if you customize a specific feature, for instance speed dials, you can add only your overrides to the skin, and leave the rest blank. The advantage of this approach is that we can update the standard skin and your skin will continue to work, unless we change the code underneath.
TL;DR
Do not use the standard_skin.zip as a base for your custom skin, instead create a minimal skin with only the changes you want.
Dustin WilsonKhadgar # Tuesday, January 18, 2011 6:22:14 PM
I'm unsure if that's as necessary anymore because regular skins (on the Mac) now can't skin the scrollbars, list headers, etc. (and I like that) The only thing that I've been scratching my head about (and I haven't checked) is that on a lot of regular skins (with no native designations inside the skin) when applied on the Mac have screwed up search inputs — such as the standard skin. Because I haven't checked closer to see as I haven't worked on skinning much lately I'm assuming it's because it's expecting to fall back to something in the system and doesn't skin that particular part.
Henrik HelmersHelmers # Tuesday, January 18, 2011 8:26:51 PM
Jimtoyotabedzrock # Tuesday, February 15, 2011 10:36:29 PM
To find the the duplicate section use the Code Explorer on the sidebar of RJEdit - http://www.rj-texted.se/index.html
It makes it easy to find the duplicates.
Henrik HelmersHelmers # Wednesday, February 16, 2011 8:50:39 AM