dealii documentation

[Praveen C]

Dear all

The documentation is now using multiple column layout which I find hard to navigate.

I liked the way it looked before.

If I want to build the documentation myself and make it look like before, how would I do this ?

thanks
praveen

[Wolfgang Bangerth]

Praveen:
if you configure with
cmake -DDEAL_II_COMPONENT_DOCUMENTATION=ON <...>
you can then do
make documentation, and it will call doxygen to create all of the
documentation locally.

That said, I'm not sure where we use multiple-columns. Can you point to an
example?

Best
W.

[Praveen C]

Hello Wolfgang

When I download doc and open it locally, I see

This is less of an issue.

More than this, the need to scroll horizontally on almost all pages is making it hard to read.

If the return type of one function is too long, then you need to scroll quite a bit to the right to read the actual content, unless you are on a very big screen.

e.g.

https://dealii.org/current/doxygen/deal.II/namespaceDoFTools.html

The scrolling was much less needed in the old template.

Functions are listed in two columns

TEMPLATE

RETURN_TYPE  |  FUNCTION_NAME(ARGS)

A layout like this would reduce horizontal scrolling

TEMPLATE

RETURN_TYPE

FUNCTION_NAME(ARGS)

I think I need to play with the css files to change this.

best

praveen

--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en
--- You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dealii+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dealii/afb32290-cd18-4b29-9177-1a10f96ca223%40colostate.edu.

[Marc Fehling]

Hi Praveen,

doxygen added these navigation columns by default as a new feature in version 1.13.0. With pull request #18932, those will be disabled for the deal.II documentation.

I believe we adjusted these flags on our hosted documentation already, but didn't update it in the dox file in our repository.

Best,
Marc