|
OversightSkins
Oversight has a limited Skin capability. It comes in the form of templates with macros to replace certain text within html and css pages. Modifying SkinsOversight comes with two skins, both of which are immature at the moment.
You can modify the alt skin but you changes will get wiped when upgrading. Alternatively you can create a copy of the alt skin, and make you changes there. To do this simply copy the entire folder /share/Apps/oversight/templates/alt to a new folder .eg. to create a skin called 'myskin' /share/Apps/oversight/templates/myskin Then change the oversight skin setting ovs_skin_name in /share/Apps/oversight/conf/oversight.cfg from 'alt' to 'myskin' Background ImageYou can set you own background image for
Main Menu BackgroundFirst it is important to understand that Oversight displays different image depending on the display device. This is due to Gaya browser limitations , and also to a PAL aspect ratio bug. So if you have SD devices , you will need to create an SD background image, wihch can just be a scaled down version of the HD image. Or you could use the HD image for SD and accept that it will be cropped when viewing on an SD screen. In the following example skin_name is replaced with the name if the skin you are modifying. You can modify the 'alt' skin directly, but if you want changes to be preserved during upgrades, then you should make a copy of the alt skin, and change that. To change the main menu background. First edit /share/Apps/oversight/templates/skin_name/any/menu.template and change <body [onloadset=:START_CELL:] focuscolor=yellow focustext=black class=menu_background > to <body [onloadset=:START_CELL:] focuscolor=yellow focustext=black class=menu_background background=[:IMAGE(black_desert.jpg):] > Then check the main menu page displays the black_desert image, rather than a plain black screen. Now you can change the image. Put a suitable background image in the following folder:
and change the template file (/share/Apps/oversight/templates/skin_name/any/menu.template) to reference your new file instead of 'black_desert' This may need a fix for C200 / 1080 mode. MacrosThe template system is like the C-PreProcessor. It takes a file in, and replaces certain bits of it (MACROS), and spits out the results. Before rendering a html or css page, it is passed through the macro processor. The syntax is not very nice. (I may overhaul this one day).. eg. <h3>[:$%TITLE:]</h3> will display the title of the current video inside of <h3> tags. The exact definition is [optional bit1:macro name:optional bit2] The optional bits are only displayed if the results of 'macro name' are defined. Simple MacrosSimple Macros are replaced with a single piece of text which may be a html query parameter, a value in the oversight dayabase, or a configuration file value. Simple Macros have a 'dollar' character immediately after the first colon.. [:$macro:] HTML Query Parameter valuesFor HTML Query macros the $ is followed by '?'. [:$?name:] eg given http://popcorn:8883/oversight/oversight.cgi?view=movie URL [:$?view;] will display "movie" Media fields (title, file, watched etc)For Fields from the Oversight database the $ is followed by '%'. [:$%field:] eg given Movie 'Transformers' [:$%YEAR:] will display the year '2007' For TV listings only the first item is used. This needs to be improved. Configuration ValuesFor Fields from Configuration files the $ is followed by ovs, catalog or unpak . [:$ovs_option_name:] [:$catalog_option_name:] [:$unpak_option_name:] Compound MacrosCompound macros are specialist macros that do a specific task. eg. display a list of TV episodes in a certain format [:TV_LISTING:] Compound macros do NOT have a dollar character. Macro IndexFor a full list see SkinMacroIndex I may overhaul these macros to be more flexible, at present the bes documentation is to look at the existing templates and the macro_init function in the source code. IssuesAt present there are a number of things that hold back general skin development:
| |||||||
|