Re: [eigen] (Web Developer needed) our CSS is crappy

[Benoit Jacob <jacob.benoit.1@xxxxxxxxx>]

2010/10/15 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
> here is the current half cooked diff, I'm too lazy to file a bug for that...

It's OK, I really should have filed a bug myself instead of posting to
the mailing list, it takes a while to adjust to the new system :)

I wanted to say that your screenshots look very cool.

I'll try your patch tomorrow.

> Also, I'm not a big fan of the default doxygen style, especially the
> blue gradients and the round corners, but the pb is that's really
> painful to port such modifications from one doxygen version to the
> other. In other words I'm not sure that's worth the effort to adjust
> the default settings...

Yes, I agree it's not really worth it, it's not the most important
issues anyway (the tables-being-hard-to-read issue is more important)
and it's also largely a matter of taste, while we have other
non-matter-of-taste issues to fix first.

 Benoit

>
>
> gael
>
>
> On Fri, Oct 15, 2010 at 6:02 PM, Gael Guennebaud
> <gael.guennebaud@xxxxxxxxx> wrote:
>> 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
>>>
>>>
>>>
>>
>