[Doxygen-develop] Pages directly follow the mainpage; possibility to enable old style neaded

[<Eck...@t-...>]

Hello Doxygen Developers.


If I take a look to the change-lock of doxygen I find the following
Information:


Doxygen Release 1.5.5
(release date 10-02-2008)
Changes:
Pages created with @page are now chapters in the LaTeX and RTF output
and treeviews, and directly follow the mainpage. ...


And that's exactly what doxygen 1.5.5 does. So this is not a bug this is
a feature. But without a possibility to disable it, this is a bad
feature. There are good reasons to offer a possibility for placing pages
as top-chapters. But if you have implemented a documentation-process
where normal pages are used to hold attached information as appendix the
new doxygen-release is not useable anymore. Some of us have now
"thousands" of single pages on the top-level of the tree view or
chapter-hierarchy, which contain only additional information. As we say
in Germany "Because the trees you are not able to see the forest
anymore." Before release 1.5.5 these pages where hidden under the
book/chapter "related pages". 


We need urgently a possibility to restore the old style with the
chapter/tree-level "related pages" via the configuration of doxygen,
something like:

            USE_RELEATED_PAGES=YES/NO


For the future, I suppose also the implementation of a command

                          \inpage <pagename style="margin:0px;"> 

similar to the command \ingroup. 

Currently the only way I know to add a page as sub-page is the command
\subpage. But this is used in the definition of the super-page that
holds the link to the sub-page. This means you have to work on 2 places.
You write your page on one place of the documentation and than you have
to add the command \subpage on another place of the documentation. If
you have a small project and you work alone this may be acceptable. But
if you work in a great project as a member of a team this means that 2
persons have to write the documentation of on thing. One person writes
the documentation itself and than he calls the one who is responsible
for the backbone of the documentation because this person has to add the
new page as sub-page. 


Kind Regards,

               Eckard Klotz.