Split FEAScript into modules?

[nikoscham]

Would a fully decomposable architecture be more appropriate for the development of FEAScript (similar to the stdlib ecosystem)? The idea would be to split the system into modular packages so users can select and combine APIs depending on their needs. Below is a rough proposal for how the modules could be structured:

---

1. FEAScript-core

• Numerical methods
• Meshing tools
• Core utilities used across the ecosystem
• Basic post-processing functionality

---

2. FEAScript-models

• Implementations of physical models (e.g. heat transfer)
• Boundary conditions
• Examples and benchmark models

---

3. FEAScript-visualization

• Mesh rendering
• Advanced post-processing (e.g. with VTK.js)

---

What do you think about this approach? Also Would a fully modular architecture make FEAScript more flexible and maintainable? Are there other modules that should exist (e.g. IO or meshing)?

[nikoscham]

Just to clarify.
Even if FEAScript does not finally adopt a fully decomposable architecture (which is still under consideration), it is built around the concept of reusable code. In particular, aside from the physical model implementations in the src/models directory, the source files in other parts of the codebase (e.g. src/mesh, src/methods, src/visualization) are intended to remain modular and reusable (although the project is not 100% there yet).