ablindgibsongirl said:
...I want to do retro mod builds for people like me who want a real computer without all the nonsense.
Might be better to define a reasonably ideal system with features that would be best.
Its probably easier to define a new retro system than to do add-on on vintage systems... and with a new design, its got a lot more use left in it.
Things that may affect such a definition of features:
Voice storage and playback and
synthesized sound isn't too expensive and we have cheap integrated circuits that can store unbelievable amounts of that sort of data. So listening to an computer Operating System is practical.
However talking-in commands is not as successful today. Some may counter that Dragon brand-software running on a melt-down core processor can do a good job, but if we're talking vintage, we're really not talking about that much processing power.
Accelerometers are much better than the ones applied in WII games, the problem with using motion based input is that acceleration isn't something that people really grasp in all aspects; its a fast car to most people. And relating acceleration to motion is not as direct as most assume.
An
optical motion tracking detector is probably more sensible. A collar-mount camera could track hand motions via a ring or bracelet on each hand... if it has a blinking infrard LED... all the easier.
A
keyboard is a good text input device, I seldom look at the screen when I'm typing (and I have the typos to prove it).
Perhaps
a mouse that gives relative position by two changing tones - perhaps X axis by changing frequency and Y axis by changing amplitude of another tone... easy to synthesize. When the mouse pointer crosses over an icon the operating system could sound it out... until another icon interrupts and starts its Id. A quick shortcut would be to lead with a short click tone-pattern ID indicating the icon type so when you hear that, you immediately know if its not what you're looking for... a quick audio shortcut.
- - -
Its an interesting idea too, because a sound.display would allow working some vintage type applications with no monitor display. That would add to mobility ease, particularly with a bluetooth earpiece... i.e. working on a subway with no monitor for display... I could imagining entering firmware code with a pair of keyboard mittens instead of a bulky keyboard while listening to the sound.display and mouse.