[Comoblog-commit] modules/mod_skinselect/templates/top mod_skinselect.tpl.htm,NONE,1.1
Status: Inactive
Brought to you by:
markwallis
|
From: iamdecal <iam...@us...> - 2006-02-24 00:01:37
|
Update of /cvsroot/comoblog/modules/mod_skinselect/templates/top In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13177/mod_skinselect/templates/top Added Files: mod_skinselect.tpl.htm 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.tpl.htm --- <!-- BEGIN: main --> <select name="mod_skinselect" class="topbar_selector" onchange="if(this.value!='nolink') location=this.value;"> <option value="nolink">Change Layout</option> <!-- BEGIN: item --> <option value="index.php?useskin={ITEM.skinselect_nav_link}">{ITEM.skinselect_nav_text}</option> <!-- END: item --> <option value="/">PHP Default</option> </select> <!-- END: main --> |