History of TemplateChangelog
Version 22 | Current version | |
---|---|---|
Things that need to change sooner or latertidy up and separate navbar linksuse <ul><li> to be in accordance with w3c and wcag recommendations and it also allows for amazing styling possibilities using css
use fisheye for bannersallow for package specific banner inclusion. this will override whatever is set in the css and thus the css setting will be visible whenever no image is set for a given package.we can do this using css properties, which i think is the more elegant way, compared to including the image inline and it allows for text placement above the background image: <div class="top" style="background-image: url($foo); background-position: top left;">...</div> advantage of inline CSS: this option could be a checkbox in every package's settings this could also become a page-specific inclusion page specific classesdiv class="content display PageName" ... for page specific styling, comes in handy when only one listing in a page should look funky, or the 4th image of the 2nd gallerytables and their headerswe really need to sort out these friggin table headers and the sort links. it's impossible to debug these endless links in the tpl files with all the conditions.i propose we pass a comma separated list of values to a smarty function, which does the rest the template stuff:
additional notes: to view a full list of options please see the file kernel/smarty_tiki/function.smartlink.php reducing number of divsthe number of divs used in tikipro is still a bit excessive. perhaps we can find a couple more places where these can removed / changed to something else:<div class="box"> <div class="boxtitle">foo</div> <div class="boxcontent">bar</div> </div> could become: <div class="box"> <h3>foo</h3> <p>bar</p> </div> would allow for same amount of styling freedom. the only downside is that <p> doesn't allow block elements in xhtml, which means that we have to close off </p> before adding divs and lists minor changesusing .current instead of .selectedbetter choice of words and isn't as similar to select progressalready integrated into clydemaking tabs optionalthis means that it should be possible to disable the inclusion of the tabs javascript file.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 them. 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 classesoutermost 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. | 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
|