#604 move reference element related stuff to separate module
Metadata
Property | Value |
---|---|
Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
Reported at | Sep 25, 2009 09:52 |
Type | Feature Request |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Last edited at | May 10, 2012 12:38 |
Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Closed at | May 10, 2012 12:38 |
Closed in version | 2.2 |
Resolution | Implemented |
Comment | The remaining sub-tasks have their own spin-off tasks #959 (closed) and #1102 (closed). |
Description
This is a replacement task to #538 (closed): instead of moving things to dune-common, we could introduce a new dune module (name suggestions welcomed) which contains:
- parts from the generic geometries (generic construction classes, corner mappings...)
- the geometry type
- the generic reference elements
- the quadratures
- a geometry interface class
- ... both dune-grid and dune-localfunctions would depend on this module. It would increase the non-monolithic design (removing geometry type from dune-common, quadratures and reference elements from dune-grid) and would make the dependency between modules a lot clearer.
The transition could be done smoothly by adding deprectaed headers in the appropriate places.