History of TemplateChangelog
Version 33 | Current version | |
---|---|---|
at the moment, these suggestions are mostly meant for the dillinger release, as they would cause too many backwards compatibility problems if applied in ReleaseOne. please raise any concerns / ideas you have as comments at the bottom of this page. already underway in ReleaseOne.contain and .admincurrently every page has a div wrapper with the following:class="<content type=""><relevant class="" such="" as="" wiki="">" currently content type is either .contain .admin we have decided to change these classes to .display .listing .edit .admin API changesReplacing tabs HTML with smarty block functions 2005-05-09i have just replaced the existing html tabs code with smarty block functions. now, all you need to do to get tabs on your page is use the following code:
The reason why we do this, is to allow for a simpler template code, an easier, centralised control of the tabs code and an easier way of changing to a different tabs script if needed. $areaName to $textarea_id 2005-05-15due to the introduction of the WYSIWYG editor PackageTinyMCE we need to specify what textareas should be targeted with the editor. this is done by assigning the id of the textarea to $textarea_id. (used to be $areaName).dillinger progresstheme uploadi have just uploaded a theme called olfactory, which contains templates that will most likely be applied as soon as we have a dillinger branch. the reason for this is, that we have decided not to waste time updating old themes - perhaps only 1 or 2 with every version. this might seem radical, but tastes change and nowhere as much as on the web. in addition, new themes are generated relatively quickly and frequently.if there are many requests for the maintenance of any given theme, i'm sure we can find someone willing to maintain it. olfactorythe olfactory theme contains custom template files for some prominent packages such as wiki and blogs. if you are interested you can get a copy of the theme from cvs. i can't post a copy here as the theme is currently in constant flux and anything here would outdate rather quickly if i don't upload a new version almost daily.additionally, we are planning on rewriting the theme structure. please see ThemeStructureIdea2 for details. package specific classoutermost wrapper around entire applicationdiv id="wrap1 {$gTikiLoc.ACTIVE_PACKAGE}" ... package specific styling, totally cool due to the nature of the ID tag as a unique identifier, it can't have a space separated list of selectors. for this reason i have opted for the following: div id="wrap1" class="wrap-{$gTikiLoc.ACTIVE_PACKAGE|lower}" ... this should not cause any compatability issues (keeping everything lower case for netscape) and the classname is unique as well. Future changestidy up and separate navbar linksuse
| at the moment, these suggestions are mostly meant for the dillinger release, as they would cause too many backwards compatibility problems if applied in ReleaseOne. please raise any concerns / ideas you have as comments at the bottom of this page. already underway in ReleaseOne.contain and .admincurrently every page has a div wrapper with the following:class="<content type=""><relevant class="" such="" as="" wiki="">" currently content type is either .contain .admin we have decided to change these classes to .display .listing .edit .admin API changesReplacing tabs HTML with smarty block functions 2005-05-09i have just replaced the existing html tabs code with smarty block functions. now, all you need to do to get tabs on your page is use the following code:
The reason why we do this, is to allow for a simpler template code, an easier, centralised control of the tabs code and an easier way of changing to a different tabs script if needed. $areaName to $textarea_id 2005-05-15due to the introduction of the WYSIWYG editor PackageTinyMCE we need to specify what textareas should be targeted with the editor. this is done by assigning the id of the textarea to $textarea_id. (used to be $areaName).dillinger progresstheme uploadi have just uploaded a theme called olfactory, which contains templates that will most likely be applied as soon as we have a dillinger branch. the reason for this is, that we have decided not to waste time updating old themes - perhaps only 1 or 2 with every version. this might seem radical, but tastes change and nowhere as much as on the web. in addition, new themes are generated relatively quickly and frequently.if there are many requests for the maintenance of any given theme, i'm sure we can find someone willing to maintain it. olfactorythe olfactory theme contains custom template files for some prominent packages such as wiki and blogs. if you are interested you can get a copy of the theme from cvs. i can't post a copy here as the theme is currently in constant flux and anything here would outdate rather quickly if i don't upload a new version almost daily.additionally, we are planning on rewriting the theme structure. please see ThemeStructureIdea2 for details. package specific classoutermost wrapper around entire applicationdiv id="wrap1 {$gTikiLoc.ACTIVE_PACKAGE}" ... package specific styling, totally cool due to the nature of the ID tag as a unique identifier, it can't have a space separated list of selectors. for this reason i have opted for the following: div id="wrap1" class="wrap-{$gTikiLoc.ACTIVE_PACKAGE|lower}" ... this should not cause any compatability issues (keeping everything lower case for netscape) and the classname is unique as well. Future changestidy up and separate navbar linksuse
|