samurai@cs.mcgill.ca (Darcy BROCKBANK) (06/08/91)
For a technical programming project I am planning on making a virtual window space interface for the NeXT. That is, the screen will be a large window looking onto the window space. You will be able to move the screen about the window space and perform all other tasks normally. Hopefully I will then extend this to a double screen interface, where the window space will be able to be accessed through two machines, two screens (one a master, the other a slave perhaps) and one keyboard+mouse (the master's.) Being relatively new to NeXT (5 months) I do not know off the bat if this will conflict with the normal operation of the machine (I am particularly concerned with the Window Manager.) So, while I am in the thinking phase I would like to entertain suggestions regarding: 1) Feasablity and Practicality issues regarding programming. Which approaches to follow, and which to avoid. 2) Usefulness. Would you or would you not find this a useful tool? 3) Suggested features to implement. In particular maintaining ease of use; a common sense approach to engineering the interface. 4) Possible conflicts with the resident processes on the NeXT. All responses will be useful to me, however short or lengthy. Thanks in advance. - db -- samurai@cs.mcgill.ca