|
|
!! page specific classes
|
-__div 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 gallery
|
+__div class="display <Package> <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 gallery |
|
|
-!!tables and their headers
|
+!! making tabs optional |
+this means that it should be possible to disable the inclusion of the tabs javascript file. some minor tweaks of the appropriate css files should make die forms display quite nicely. |
+ |
+ |
+!! 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}
|
+{code source=Html4Strict} |
...
|
-<th>
|
-{smartlink ititle="foo" isort="title" isort_mode=$sort_mode}
|
-</th>
|
+<th> |
+{smartlink ititle="foo" isort="title" isort_mode=$sort_mode} |
+</th> |
...
|
-{code}
|
+{/code} |
additional notes:
|
to view a full list of options please see the file
|
kernel/smarty_tiki/function.smartlink.php
|
|
|
-!!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>
|
+!! reducing number of divs |
+the number of divs used in bitweaver is still a bit excessive. perhaps we can find a couple more places where these can removed / changed to something else: |
+{code source=Html4Strict} |
+<div class="box"> |
+ <div class="boxtitle">foo</div> |
+ <div class="boxcontent">bar</div> |
+</div> |
+{/code} |
|
could become:
|
-<div class="box">
|
- <h3>foo</h3>
|
- <p>bar</p>
|
-</div>
|
+{code source=Html4Strict} |
+<div class="box"> |
+ <h3>foo</h3> |
+ <p>bar</p> |
+</div> |
+{/code} |
|
-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
|
+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 changes
|
-using .current instead of .selected
|
-better choice of words and isn't as similar to select
|
+{code source=Html4Strict} |
+<div class="header"> |
+ <h1>foo</h1> |
+ <div class="date">bar</div> |
+</div> |
+{/code} |
|
----
|
+could become: |
+{code source=Html4Strict} |
+<div class="header"> |
+ <h1>foo</h1> |
+ <p class="date">bar</p> |
+</div> |
+{/code} |
|
-!progress
|
-!!already integrated into clyde
|
-!!!making tabs optional
|
-this means that it should be possible to disable the inclusion of the tabs javascript file.
|
|
+!! themes manager |
+since the structure of themes is changing considerably, we should change the user interface as well. |
+the first coice will be how many columns should be present on your site (one, two or three). after this, you are taken to a page that has a set of styles you can choose from. every style is accompanied by a small screenshot of the given style (perhaps 150x150px or so). |
|
-!!dillinger 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 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.
|
+!!! deleting themes |
+there will always be an option to delete a given style from your server, but not an entire theme. this is way too radical and might cause the unwanted loss of styles. if a given theme doesn't contain any styles, it isn't displayed anymore for selection. |
|
-!!!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.
|
+!!! editing themes |
+due to the complexity of the css files, i'm not sure how to deal with a css editor. perhaps it's best to just use a textarea that allows users to edit a copy of the css file directly, and allow the upload of images that can be used. |
+i will try and simplify stylist and get it working again soon. |
|
-additionally, we are planning on rewriting the theme structure. please see ThemeStructureIdea2 for details.
|
+!!! term definitions |
+;theme:a theme is the basic definition of what the layout of the page should be, such as the number of columns, which in general can range from 1 to 3 columns. |
+;style:a style is the look and feel of the site without interfering with the layout. |
|
-!!!package specific class
|
-outermost wrapper around entire application
|
-__div id="wrap1 {$gTikiLoc.ACTIVE_PACKAGE}"__ ... package specific styling, totally cool
|
+!! minor changes |
+using .current instead of .selected |
+better choice of words and isn't as similar to select |
|
-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. |