Support and General Use > Theming and Appearance Customization

ui viewport, custom statusbars and backdrops

(1/4) > >>

JdGordon:
almost cut/paste from the dev ml... I'm fixing the way backdrops are handled by skins (including the sbs) and I've hit a snag. In svn the sbs cant load a backdrop which is fine, the setting then is *always* shown unless the WPS displays its own backdrop. This breaks with plugins which have the backdrop disabled (because most wont work with the users backdrop).
The problem is the menus in those plugins then enable the theme again but they look crap because the backdrop is disabled.

Now, I have 4 options how to deal with this. In all of them the "theme" includes the custom statusbar and the ui viewport and colours, etc. The main time you will see a theme disabled is in plugins.

option 1) "backdrop setting always takes priority, backdrop shown when theme is disable" -- if the .sbs loads a backdrop, and the user specified a backdrop in the settings, the sbs one will be ignored. whichever backdrop is loaded will *always* be displayed unless another skineed screen (WPS) loads its own backdrop.

option 2) "setting takes prioty, no backdrop shown when theme is disabled" -- same as 1) except no backdrop will be displayed when the theme is disabled (plugins, a wps with %wd, etc). This is my prefered option

option 3) "sbs backdrop takes priority, setting backdrop shown if theme is disabled" -- same as 2) except the sbs backdrop will be used even if a setting backdrop has been specified.

option 4) "sbs backdrop takes priority, nothing shown when theme is disabled" -- if the .sbs and setting both want a backdrop BOTH are loaded into RAM, when the theme is enabled the sbs backdrop is shown, when its disabled the setting one is shown, in the WPS the wps one is shown. This will almost certainly not happen because of the extra RAM use needed.

If you choose option 5 and dont leave a comment I'll hunt you down and... well... it wont be pretty....


without wanting to sway the vote too much, option 2 is my prefered, 1 is the next best (but this will mean lots of extra work for plugins).... so vote 2!

GodEater:
I don't know and don't care :)

fml2:
I think that it's wrong to have two sources for the backdrop image. Why not have just one (i.e. allow the backdrop to be set either only via sbs or only in the setting)? Then there will be no confusing for the user, and the implementation will be simpler as well.

AlexP:
I'm confused just reading the options given.

fml2:
And my general feeling is that the recently introduced features (custom UI, sbs) have unnecessarily complicated things. Before, nearly 100% of users understood how it works, now, I think, it's 20% at best. May be this is because it's not clearly documented.

Navigation

[0] Message Index

[#] Next page