| Re: [eigen] (Web Developer needed) our CSS is crappy |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] (Web Developer needed) our CSS is crappy
- From: Gael Guennebaud <gael.guennebaud@xxxxxxxxx>
- Date: Fri, 15 Oct 2010 18:02:43 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=JlezMQgJozkcN+SVQhwZ//HaCRdt65NGy8iLO9KSq6Y=; b=FqgxvqXqihpOsf72Z9fZgrn/yy2nVKQEZlfjA1GaJLDDupe6m1khEd6Hm1V3teZA7T GXCS4rfsekE1Vf9wvU0IvfyB/Thtk143XHMpGCaxF6gZAwHtrS+r7+u/iJWotmXKN9/A MocoCp0GQ7/A/cPCxm5j5EnMCBE5lBzQ3ov7A=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=j99bpZr32rhWO1HVGZczyTpBZCH1sDN9krNGQHJ0EKetuG8xUOza9J72KtzQ+V2j/4 my8J5Hje2+Wc3wX8uAA++9c91H/DqQpCvJBH5t5CzeAViVagoBAISLtTVNJgEOvS0nBU XTQLe+H+Uveup7vgJk6IdDiovDCYHPsYyBMXM=
indeed, there are many problems:
1 - the .css file corresponds to old doxygen version, while it is now
generated using doxygen 1.7.x
2 - the class attribute of many tables was not specified
3 - we don't use the <th> tag for headers
etc.
so on my local copy I fixed many of these issues and you can see some
screenshots there:
http://dl.dropbox.com/u/260133/eigen/new_style_01.png
http://dl.dropbox.com/u/260133/eigen/new_style_02.png
http://dl.dropbox.com/u/260133/eigen/new_style_03.png
Basically I've re-started from scratch with default doxygen 1.7.2 css
file, defined two table classes:
"example" for example/output tables
"manual" for the default tables of the manual
and added some space + one line for section headers.
This can be improved further but I think that's already a better start.
gael
On Fri, Oct 15, 2010 at 3:03 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
> Hi,
>
> while updating the Eigen2To3 porting guide I realized that we need
> someone with more CSS skills AND good taste to have a look at our CSS.
>
> Case in point: http://eigen.tuxfamily.org/dox-devel/Eigen2ToEigen3.html#Decompositions
>
> there are many problems in this table :
>
> 1. it's not even clear at first glance that it's a table. Borders would help.
>
> 2. but borders could easily make it feel clumsy and in other tables e.g.
> http://eigen.tuxfamily.org/dox-devel/Eigen2ToEigen3.html#PartAndExtract
> borders are not needed because each cell's content has its own border.
>
> --> maybe we need a separate table class for this latter case i.e.
> when all cells have their own rectangle
>
> --> but maybe there is something smarter that a real web developer
> would do. For example, use smart background colors to make the table
> structure apparent without resorting to borders??
>
> 3. the column headings ("Eigen 2", etc) are not visible enough. Make
> them bigger? bold?
>
> 4. the "#include..." cell on the bottow row is too big, gets too close
> to the next cell, it's ugly. Is this is place where one needs to
> adjust cell padding/spacing?
>
> Then we have more non-table-specific CSS issues:
>
> 5. There is not enough whitespace before a new section, especially
> after a large table. Makes the document structure hard to see.
>
> 6. We use all the horizontal size of the browser window. While that is
> useful for large tables, this makes paragraphs of text hard to read.
> Ideally we'd limit the width of the area that we use, except for
> tables (all tables ? or only certain explicitly specified ones?)
>
> Benoit
>
>
>