CssChangelog

CSS file changes

Created by: xing, Last modification: 02 Dec 2005 (11:39 UTC)
list of changes that have occurred in the template files that have an impact on css files

Finally we have the templates more or less in a usable state and we are now starting to document template changes that affect css classes globally.

ReleaseTwo CSS changes

all changes made in dillinger will be documented with a substitution expression to make upgrading from one version to another as simple as possible. the reason why we have to make changes at all, is because bitweaver is evolving rather quickly and we need to adjust to the demands set by the users. styling should be simple, but should also be flexible. personally, i think we are on the right track to achieving this goal.

all the substitution strings are meant for vim

so, if you are planning on upgrading a theme from ReleaseOne to dillinger, please read the following section carefully.

before you make any changes, please make sure you make a backup copy of your theme.


2005-05-07 - xing

  • conversion of .navbar to different types of bars
    • tabs --> class="pageactions tabs"
    • tools --> class="pageactions tools"
    • sorting --> class="pageactions sort"
    • for more information view TemplateChangelog
{code()}
:%s/\.navbar/.pageactions/g
:%s/\.above//g
:%s/\.below//g
{code}
to further differentiate between the different types of pageactions, you can use the .tools .tabs and .sort selectors.



ReleaseOne CSS changes

2005-12-01 - xing

remove last occurances of .tiki in class and id names in all template files and replace it with .bit

2005-04-22 - xing

  • moving from .contain and .admin to .display, .edit, .listing and .admin
    • for more information view FutureTemplate

2005-02-05 - xing

  • some tables are replaced with easily viewable item listings that contain a lot of data. tables are cumbersome and not practical when viewing a lot of data at once.
{CODE()}

  • item 1

  • item 2

  • item 3


{CODE}

2005-02-03 - xing

  • forgot to mention that we want to change the navbar from just being links, into a
    • list of items. this is backwards compatible with the previous system. so it's:
    {CODE()}

{CODE}

2005-02-02 - xing

  • decided to replace and expand the containing dev classes. currently we only use .admin <pkg> and .contain <pkg>. this will be changed to
    • .admin <pkg>
    • .edit <pkg>
    • .listing <pkg>
    • .display <pkg>

2005-01-26 - xing

  • added the class .menu to the top menu bar. this is now conform with other menus in tp

2005-01-24 - xing

  • removed inclusion of base.css from the section. you can still use base.css by adding
    @import url('../../base.css');
    to the top line of your css file (has to be line 1)

2004-12-28 - xing

  • removed any occurances of target="..." since that attribute isn't allowed in XHTML 1.0 Strict anymore
  • introduced new class="external" for links leaving site. this class can be used to highlight links that leave the site to 'warn' the user (currently style is set in base.css)
  • internal links don't warrant a special class as all links are considered internal.
  • removed more pesky tikiwiki classes
    • tikilink
    • rsslink
    • rssitem
    • ...

2004-12-13 - xing

  • changed div .appmenu and .admenu to .menu
    (it is still possible to access these module individually by using the unique module css class)
  • above change makes it possible to use .head and .item for the menus instead of .menuhead and .menuoption
  • to update your custom css file do the following:
    .menuhead --> .menu .head
    .menuoption --> .menu .item
  • menu structure has also changed somewhat to accomodate for the new css driven dropdown menus. all menus are now unordered lists. this should not concern you though, as the basic styling of the list is taken care of base.css. see ReleaseOneChangelog
</pkg></pkg></pkg></pkg></pkg></pkg></ul>