The keyboard model is tied to the use of source code, and source code to the keyboard. This implies wholesale replacement of source code. Probably with an ico

The keyboard model is tied to the use of source code, and source code to the keyboard. This implies wholesale replacement of source code. Probably with an icon-based language and drag and drop development environment. This also implies a substantial library of icons be available for various common tasks; of very substantial task abstractions. Classic development and debugging and tracing models are all tied to the screen space. This implies having extra display space available that can be slid into view on demand whether for selecting tasks or for tracking, or a requirement for in-band debugging displays, or removing the need for debugging and tracing. You will need to build a box of task blocks, an icon drag-n-drop IDE, and icon-based debug and trace. And you will want ancillary pieces, including dump and trace and update tools. In Apple Xcode terms, a gonzo and finger-based and viewport-constrained IB. Sounds fun.