Skip to content

How it actually turned out

Sadly, after starting to implement the planned MVC- & Observer-Pattern, I found out that my plan of fully using OOP for the project failed, since Textual uses a mix of Object-Oriented aproaches and static classes and methods.

Also, it turned out to be really complicated and time-consuming to import classes from .ipynb files.
Therefore I discarded the notebooks and control.py. The remaining classes were copied to model.py

I still tried to use the interfaces, although there wasn't enough time, so I had to hardcode a bit. Also Python doesn't support realization natively and the ABC Metaclasses (which i used for the interfaces) don't support realization.

The GUI turned out (mostly) how it was planned.

Packaging and building the release was done with hatch.

Documentation was generated with mkdocs and mkdocstrings.

UML