[Dune] Moularization

[Peter Bastian]

Dear all,

Christian has done a great job in the last two weeks to introduce the
modularization of dune. I think this was a good and important step. But 
now help is needed by all developers to get out 1.0 soon.

The TODO file in the appendix of this mail lists the things that are 
left. Please, let us discuss who can do what on this list.

Best,

-- Peter + Christian
------------------------------------------------------------------
Peter Bastian, IWR,Uni Heidelberg, INF 348,R 020, 69120 Heidelberg
email: Peter.Bastian at iwr.uni-heidelberg.de   Tel: +49 6221 54 4984
WWW: http://www.iwr.uni-heidelberg.de/~Peter.Bastian Fax: ... 8860

-------------- next part --------------
1) Issues with core dune:
-------------------------
dune-common:
  * The build system only works for a dune tree from the svn. The
    configure tests have to be updated to search also for an installed
	Dune. (Markus already said, that he will work on this)
  * The dune-project script does not work anymore. Someone has to
    update this script to the new build system.
dune-grid:
  * io and quadrature have to be integrated into the grid directory.
    (Christian will do this immediately)
dune-grid-howto:
  * The build system has to be updated:
    - create a dune.module file
    - update autogen.sh and configure.ac
    - remove am directory
  * move grid-howto from CVS to subversion
  * rework the tex files
  (Peter will work on these issues)

2) Issues with the web site / Documentation:
--------------------------------------------
* We must check that each module properly installes it's
  documentation:
  - After configuring a module with --with-duneweb=... you should be
    able to call make web-install in your projects doc directory.
  - doxygen documentation should not be installed in the web directory
* dune-web should include a doxygen documentation of the whole
  Dune. Therefore dune-web must be extended:
  - We need Doxyfile in the appropriate directory. This Doxyfile
    should not include the source directories, but should instead have
	an include statement for a file containing the list of source
	directories.
  - The list of source directories should automatically be constructed
    during the configure target of dunecontrol. As dune-web is not
	under the control of autoconf, we will have to overwrite the
	configure method in the dune-web dune-module file (see
	dune-common/dune-module for an example).
  - Doxygen should not include all source files found in the
    modules. Source code found in the doc tree, for example, should be
	excluded. Perhaps it would be the best to add an entry
	``Doxygen:'' to the dune.module file with a space sperated list of
	the files/directories to be included in thedoxygen documentation.
* The documentation of each module has to be updated
* We need a documentation of the buildsystem from a developers point
  of view (Christian is working on this)
* We need to update the installation guide and the download section.

3) Automatic test system
------------------------

Has to be updated to the new system.


4) All the application have to updated
--------------------------------------
for us in HD these are
  - dune-istl
  - dune-disc
  - dune-dd
  - dune-highres