So,
I set about filling out the SolutionTransfer system tonight... and I
realized that the code I was writing was pretty high level... and not very
libMesh like. I was hiding quite a lot and assuming quite a lot... and
providing interfaces that might not be optimal in certain circumstances.
So, here's what I'm thinking... I'm going to do away with the
SolutionTransfer system in libMesh... and undo the work I was doing. I'll
move the DTK functionality to "misc" and redo the example I added to not
use the (now deleted) DTKSolutionFunction... but just use the DTK interface
classes I made instead.
I think that the MeshfreeInterpolation stuff that Ben has in there along
with the DTK interfaces provide good library functionality. People can
wrap those up the way that want, if they want.
What do you guys think?
Derek
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
