While working on the cross-platform Qt port of emulator, I’ve run into issues with the RetroShell architecture. It’s not like it’s not working correctly, but it’s a bit over engineered and structurally too complex. A lot of the complexity comes from the fact that a server connection will hook into the emulators console (which is currently a singleton) and a lot of effort is taken such that every component sees what it is supposed to see.
In a future version of the emulator, the shell architecture should be cleaned up. By allowing multiple console instances that all connect separately to the emulator core, the internal architecture should become much simpler.
While working on the cross-platform Qt port of emulator, I’ve run into issues with the RetroShell architecture. It’s not like it’s not working correctly, but it’s a bit over engineered and structurally too complex. A lot of the complexity comes from the fact that a server connection will hook into the emulators console (which is currently a singleton) and a lot of effort is taken such that every component sees what it is supposed to see.
In a future version of the emulator, the shell architecture should be cleaned up. By allowing multiple console instances that all connect separately to the emulator core, the internal architecture should become much simpler.