SDL has been considered as hardware so the project has been coded to work directly with SDL2, no other consideration at that time.
The idea behind was SDL is the "OS/driver/HW/VGA" to code against to, but evolving the lib might not be the case anymore.
It could be the time to decouple and allow to run this as a library in some other "custom mode" with other window libraries or rendering tools... as well as to allow easier mocking and testing.
Does it make sense?
Let's say Yes,
potentially "VgaTerminal" can be used with DirectX directly or whatever for example, skipping SDL.
It could be for v2.0.0 more then v1.0.0
it requires to change the repository's name too in this case... :)
this ticket is nice also for parsing the vgaunicode format file...
to do after a "setMode" method implemented
so this is blocked by #161
SDL has been considered as hardware so the project has been coded to work directly with SDL2, no other consideration at that time.
The idea behind was SDL is the "OS/driver/HW/VGA" to code against to, but evolving the lib might not be the case anymore.
It could be the time to decouple and allow to run this as a library in some other "custom mode" with other window libraries or rendering tools... as well as to allow easier mocking and testing.
Does it make sense? Let's say Yes, potentially "VgaTerminal" can be used with DirectX directly or whatever for example, skipping SDL.
It could be for v2.0.0 more then v1.0.0
it requires to change the repository's name too in this case... :)
this ticket is nice also for parsing the vgaunicode format file...
to do after a "setMode" method implemented so this is blocked by #161