INM-6/incapy

General structure for views for different algorithms

Opened this issue · 1 comments

Different algorithms might need different data, thus different views. And the data from the view needs to be passed on correctly.

If this is implemented an object oriented approach should be chosen. This means that there should be a base view class that manages common stuff (e.g. provides an API for sending messages) and other views can subclass from that and use the common stuff.

Different views might be needed for different algorithms, and for different ways of viewing the data (e.g. Jupyter or standalone or only export video).