Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ROADMAP: Moving PyAEDT Visualization classes to a separate repository #5512

Open
Samuelopez-ansys opened this issue Dec 1, 2024 · 0 comments

Comments

@Samuelopez-ansys
Copy link
Member

Visualization classes are a core component of PyAEDT, representing one of its most significant and complex parts. By separating these classes into a dedicated repository, several benefits can be realized:

Improved Modularity: Splitting visualization classes into their own repository promotes cleaner code organization and a more modular architecture. This separation makes it easier to maintain, update, and scale the visualization components independently of the main PyAEDT repository.

Enhanced Collaboration: A standalone repository allows contributors to focus specifically on visualization features without being entangled with other aspects of the PyAEDT project, encouraging more specialized and efficient development.

Streamlined Maintenance: Isolating visualization functionality simplifies debugging and testing processes, as changes in visualization code can be managed without impacting the rest of PyAEDT.

Reusable Components: A dedicated repository makes it easier to use the visualization tools in other projects or contexts, potentially broadening their applicability beyond PyAEDT.

This restructuring paves the way for a more robust and focused approach to developing and enhancing visualization capabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Q3 2025 - Jul-Sept
Development

No branches or pull requests

1 participant