On Tue, 10 Feb 2009, Derek Gaston wrote:
>> Add something like deal.II's user_pointer to every element and node. >> More powerful, but also a little harder to deal with (e.g. how do you >> serialize to mesh files?) > > This (and Ben's templating idea) both scare the shit out of me. The > potential for abuse and problems is REALLY high with this one. Sierra has > something similar where essentially you can attach lots of data types to mesh > types. People use it for all kinds of stuff it shouldn't be used for and > then complain whenever things like "restart" capability don't work. Adding > arbitrary data to the mesh just feels like a bad idea. Hmmm.. instead of giving users a (void*) and some nitroglycerine to play with, maybe a pointer to an abstract base class with serialization functions? At least force them to be aware of what they have to do to make things work correctly. Eh, but you're both the one with the most experience with this problem and the one who'll have the most urgent need to solve it. So whatever you do, good luck with that! ;-) --- Roy ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
