refactor the css style sheets

hussayn <[email protected]> Tue, 13 Jan 2009 11:29:37 -0800 (PST)
Newsgroups gmane.comp.java.scarab.devel
Message-ID <[email protected]>
Hi;

I started reworking the css - stylesheets. 
I want to remove all parts, which are not used by scarab and
i want to remove all redundant parts.

Status quo: currently we do have 5 style sheets:

tigris.css
inst.css
scarab.css
ns4_only.css
print.css

This is what i already found so far:

- Removing ns4_only.css
  i do not see any visible difference on firefox and i guess it will be the
same for mozilla.
  IMHO the file even does not contain any ns4-specific css declarations. So
i opt for removing it.

- merging tigris.css and inst.css
  I guess, tigris.css was meant to be the default style for all tigris
software. But since Scarab has been
  moving away from the tigris defaults significantly, i guess, we can just
forget keeping tigris.css
  intact. So i opt for at least merging the content of tigris.css and
inst.css, which was meant as an
  example for adapting tigris.css I still have to check if this file is at
all relevant for Scarab.

- refactor the style sheets according to functionality rather than
compatibility.
  I guess, it makes much more sense to organise the files by function, e.g.:

  common.css
  issues.css
  reporting.css
  admin.css
  ...

1.) My first move is to temporarily merge all css related stuff into one
single .css
I will then analyse this and remove all unused declarations. I will do this
by
looking up usage of classes in the velocity-template files and remove
everything
else. My hope is to reduce the size of the .css so much, that we might not
need
to split it up again.

2.) If the remaining css-declarations of step one are separable due to
different 
functionality, i will refactor them accordingly in a secnd move.

3.) I will go through the templates and reorganize the css class system and
make it
more consistent. This may be the most tedious task, but i think it is a
necessary step
and it is still a step, which can be done without getting too deep into the
java-part.

4.) I add some primitive support for skinning.

5.) I donate the new Scarab interface, which we have designed for our
customer as
a first skin to Scarab. So my goal is to get the "old fashioned" style and
the "modern" style
become user selectable (or at least admin-selectable)

If there is any advice or help available, i would be happy to know about it
;-)

regards, 
Hussayn
-- 
View this message in context: http://www.nabble.com/refactor-the-css-style-sheets-tp21442752p21442752.html
Sent from the Scarab - Dev mailing list archive at Nabble.com.

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=1022690

To unsubscribe from this discussion, e-mail: [[email protected]].