[eigen] (Web Developer needed) our CSS is crappy |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] (Web Developer needed) our CSS is crappy
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Fri, 15 Oct 2010 09:03:29 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=OzVBu4KHU+s7Lsx2HQ3g9OEAlV7s7UO/R57D3cC3oZo=; b=XDnIA7EIVKuvqEy0+6dMEdpHn7c+KXVZjvyPtDMwxSrZo/RSrG0kVtJ3yfbqvlLqxk SgqgHxQPlp7IZLDTAGZXujFqHUsTS1DdTS3lLHODOLnwGif4wcSUyCB6A+L0TxMNYRDi zv/VgwvhcrXgQICzwg8w7x0JsQhIvjXNQAGU8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=n6R834tT+3oXydhTYchsFJJu4sRO1rL+dDjg9OAknctnOWlus8NzwlZr4CAZbfk2M9 8pHy4rCjoTAZzlkWrI4qctKKKVpxCj1FykCn7fDhfOu4vD7flcxVZh60lvfnDepA3QZq vblqVDfxpOYrJkU0RTH1TrN6Mz6Gu9FiRuf8E=
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