[Dune] [#538] dependency dune-grid <-> dune-localfunctions

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#538 - dependency dune-grid <-> dune-localfunctions
User who did this - Andreas Dedner (dedner)

----------
We have implemented generic shape function sets (for lagrange
and Raviart-Thomas and so on) using the recursive definition of the
reference elements, i.e., the Point, Pyramid<Base> and Prism<Base>
classes. Information concerning the subentities on which
to place the dofs (there types and embeddings) was also heavily needed.
The local keys used in dune-localfunction only make sense in combination
with the reference element construction.
All of this can be obtained using the classes in grid/genericgeometry
(without using the GenericReferenceElement in grid/common).
So what we would like to have in dune-common is a GeometryInterface class
and the template magic available in the genericgeometry folder.
I do not really see why any of this stuff is grid related;
I think they are more related to common (where for example
the geometry type is also located). 
In fact dune-localfunctions could be quite interesting even for people not interested in using the dune-grid interface and there is no reason why
this should not be possible without also having to use the much bigger dune-grid module. 
I actually like that dune-istl does not depend on dune-grid but can be
used seperatly. I think having modules depend on dune-common but as
little as possible on each other is a good step in a non-monolithic design.


----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=538#comment1086

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.