hi Caleb,
thanks for bringing this to my attention. It is my plan to
completely redesign the external mesh utility interface (including
data exchange format) starting in the Iso2mesh 4.0 cycle. This
will allow it to benefit from newer functions of many embedded
libraries.
over the past many years, a principle I have been following in maintaining iso2mesh is to keep it backward compatible - that means all binary utilities were fixed and the only way to add new features is to add a new binary (such as tetgen1.5 vs tetgen). While this is ok for stability, but it makes the package bulky and prevent many new functions from being incorporated.
my plan is to make the last release following this principle as iso2mesh 3.0 - with a target release date sometime this Summer - it will still be compatible with all previous iso2mesh releases. Then, in the following development cycle, I will start revamping the external utilities. This will give iso2mesh a chance to evolve and grow.
Qianqian
You don't often get email from cberg...@gmail.com. Learn why this is important
--
You received this message because you are subscribed to the Google Groups "iso2mesh-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iso2mesh-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/iso2mesh-users/9ab6f827-658b-40b2-8066-641b2f4c7777n%40googlegroups.com.