Improvement: begins with spliting the vtk writer template

Open t8ddy opened this issue 10 months ago • 1 comments

This Issue was created because the draft PR did not reference an Issue. Please @faouziH21 describe the Issue that you are solving.

Apr 04 '25 11:04 t8ddy

Currently, t8_vtk_writer is one large class that handles two cases. The first case is when t8code is linked with VTK, and the second is when it is not. This has led to large, unmanageable files that use macros to implement the class. This style conflicts with the Single Responsibility Principle; therefore, splitting this class would be very advantageous.

Apr 11 '25 10:04 faouziH21