I actually don't think it would be too hard to build a nice graphical environment for the Vectrex32 to combine both terminals into one. If I have time after these blasted exams are done I'll write it in Java and post the source to Git. I may even be able to put it into Eclipse, haha.
On another note, I recommend a hardware revision to future models of the Vectrex32 (I'll be testing this myself). Allow the thing to run off of USB power! That way 90% of testing can be done with the Vectrex off, as well as loading and accessing programs on the go. I haven't investigated voltage/current requirements yet but it can't be outside of usb capabilities. If the 32 can sense that there is no Vectrex attached it could use a set of static values for any areas the Vectrex would write to and simulate a tick counter based on its own clock. If you wanted to get really fancy you could feed it values over time but methinks that's all too ambitious at once. In order to separate the power I would just use two diodes across Vectrex and USB power input to prevent reverse biasing.
I wasn't sure whether to make it its own thread or not but I think it relates to developing on a PC environment as this potentially cuts down the required peripherals from "Vectrex32 and Vectrex" to just "Vectrex32".
Anyways, I haven't had the Vectrex32 for long so feel free to tell me off if I'm wrong.
On another note, I recommend a hardware revision to future models of the Vectrex32 (I'll be testing this myself). Allow the thing to run off of USB power! That way 90% of testing can be done with the Vectrex off, as well as loading and accessing programs on the go. I haven't investigated voltage/current requirements yet but it can't be outside of usb capabilities. If the 32 can sense that there is no Vectrex attached it could use a set of static values for any areas the Vectrex would write to and simulate a tick counter based on its own clock. If you wanted to get really fancy you could feed it values over time but methinks that's all too ambitious at once. In order to separate the power I would just use two diodes across Vectrex and USB power input to prevent reverse biasing.
I wasn't sure whether to make it its own thread or not but I think it relates to developing on a PC environment as this potentially cuts down the required peripherals from "Vectrex32 and Vectrex" to just "Vectrex32".
Anyways, I haven't had the Vectrex32 for long so feel free to tell me off if I'm wrong.