Simplification of styling

[GoogleCodeExporter]

Currently, we have a number of style files (4 in server_root, 3 more in
crunchy_tutor - some of them may be obsolete) as well as some hard-coded
styling information in some python files.

Also, the user has the option to override individual styling options by
entering some styling information in a python dict.  This method is error
prone.

Overriding default styling options is something that must be allowed for
color blind users.

I propose to have a single comprehensive style file (.css) included with
Crunchy and replace the dict option used to override styling by a mechanism
where a user enters the full path of a css file.  This would also simplify
the configuration_en.html description.

I plan to do this as part of the updating of configuration_en.html, prior
to 1.0 release.

This is tangentially related to issue 109.

Original issue reported on code.google.com by andre.ro...@gmail.com on 28 May 2008 at 3:08

[GoogleCodeExporter]

I agree, although I think we should have two files: one for all the extra 
crunchy
markup (crunchy.css - integrating the menus and so on), and another for the 
layout
used in all the documentation pages (doing what crunchy_newstyle.css does).

Original comment by johannes...@gmail.com on 28 May 2008 at 9:54

• Added labels: Maintainability

[GoogleCodeExporter]

Original comment by andre.ro...@gmail.com on 31 Aug 2008 at 10:13

• Changed state: Fixed