History of TemplateChangelog
{maketoc}
! Things that need to change sooner or later
!! tidy up and separate navbar links
use <ul><li> to be in accordance with w3c and wcag recommendations and it also allows for amazing styling possibilities using css
* tools --> move to the bottom of the page (???)
** lock / unlock
** export
* tabs --> move to the top of the page
** edit
** history
* sorting --> remain just above the table
__where do the structure and backlinks dropdowns belong?__
!!tables and their headers
we 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:
{code color=smarty}
...
<th>
{sortlink title="foo" sort="title" sort_mode=$sort_mode}
</th>
...
{code}
additional notes:
;title:the words that should be displayed
;sort_mode:pass in whatever is in $sort_mode
;sort:the name of the sort paramter of this particular link
;default:if set, will highlight this link when no $sort_mode is set
!!reducing number of divs
the 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
!progress
!!theme upload
i have just uploaded a theme called __olfactory__, which contains templates that will most likely be applied as soon as we have dillenger 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.
!!olfactory
the 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.
! Things that need to change sooner or later
!! tidy up and separate navbar links
use <ul><li> to be in accordance with w3c and wcag recommendations and it also allows for amazing styling possibilities using css
* tools --> move to the bottom of the page (???)
** lock / unlock
** export
* tabs --> move to the top of the page
** edit
** history
* sorting --> remain just above the table
__where do the structure and backlinks dropdowns belong?__
!!tables and their headers
we 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:
{code color=smarty}
...
<th>
{sortlink title="foo" sort="title" sort_mode=$sort_mode}
</th>
...
{code}
additional notes:
;title:the words that should be displayed
;sort_mode:pass in whatever is in $sort_mode
;sort:the name of the sort paramter of this particular link
;default:if set, will highlight this link when no $sort_mode is set
!!reducing number of divs
the 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
!progress
!!theme upload
i have just uploaded a theme called __olfactory__, which contains templates that will most likely be applied as soon as we have dillenger 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.
!!olfactory
the 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.