feature idea for the doctree

[Ralf Nolden]

Hi all,

as you may have noticed, I've added some pixmaps to the treehandler to
show open folders and books as well as a documentation pixmap for html
files. Now, I inserted the KDevelop user manual page by page but this
doesn't seem to be a good solution as this should be dynamic and then
can be added much easier even for the kdoc generated documentation. My
idea now is the following (but I can't realize it right now):

Could we add a parser that reads the index.html files for 
a) the User manual
b) programming Handbook
c) the kde library documentation
d) the qt documentation. (classes.html)

The project documentation must be treated different as this will change
every time. I propose to let the setup do this parsing once and store
the results in form of the book that it belongs to, the classes that the
book contains and the according filenames. On starting Kdevelop, this is
read from the configuration file and the initial doc tree build. Then
this information is stored in memory and used to refresh the tree.

The user will then work as this: a click on a book will open the index
page and changes the book icon to mini-book2.xpm(THBOOK_OPEN). On
opening the book's tree, the manual and tutorial will display their
chapters as documentation pages, the KDE and Qt doc will open their tree
of classes. About the header files we could make a subfolder which
contain these. 

Is this somehow possible to do and if so, anyone willing to ?

Bye,

Ralf