[Comoblog-commit] modules/mod_skinselect index.php,NONE,1.1 mod_skinselect.php,NONE,1.1
Status: Inactive
Brought to you by:
markwallis
|
From: iamdecal <iam...@us...> - 2006-02-24 00:01:36
|
Update of /cvsroot/comoblog/modules/mod_skinselect In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13177/mod_skinselect Added Files: index.php mod_skinselect.php Log Message: initial commit to make sure i've not missed anything transfering the code from my live site down to my cvs version basic premis is that new skins sit in css/SKINNAME/css.php of mod skin select is set to be shown then the users can change the skin via a drop down, if not then a default can be set in the admin area. these skins are imported after the rest of the css so that the content overrides and extends the existing comoblog css - i think we need to decide if skins will provide a full set of styleing or just override and extend the exising code should skin css be entered via the admin area, or uploaded (like a module) ? id prefere to upload as a module as that allows for custom images etc note need to change things like the topic icons some how --- NEW FILE: mod_skinselect.php --- <?php if (in_array('mod_skinselect', $SIDEBAR_MODULES)) $mod_pos = 'sidebar'; else $mod_pos = 'top'; require_once (CFG_BASE_PATH.'/modules/mod_skinselect/include/mod_skinselect.inc.php'); if (CFG_MOD_SKINSELECT_SHOW_SELECTOR =="Y"){ $skinselect_items = mod_skinselect_list(); } if ($skinselect_items) { $mod_skinselect_tpl = new XTemplate (CFG_BASE_PATH.'/modules/mod_skinselect/templates/'.$mod_pos.'/mod_skinselect.tpl.htm'); for ($c = 0; $c < count($skinselect_items); $c++) { if ($c % 2) $tpl->assign('BGCOLOR', '#ffffff'); else $tpl->assign('BGCOLOR', '#efefef'); $mod_skinselect_tpl->assign('ITEM', $skinselect_items[$c]); $mod_skinselect_tpl->parse('main.item'); } $mod_skinselect_tpl->parse('main'); $mod_contents = $mod_skinselect_tpl->text("main"); } else { $mod_contents = ''; } ?> --- NEW FILE: index.php --- |