Use other computers as monitor

My idea is having a advanced computer as a monitor so you can access it with mouse and keyboard and not only touch on usual monitors, this way I can have a main computer managing stuff, a access terminal and other things attached since printers to other stuff.

I don't get it, why can't you just set a computer up to do this via rednet yourself? It's quite easily possible already.

CometWolf, on 25 April 2014 - 12:39 PM said:

I don't get it, why can't you just set a computer up to do this via rednet yourself? It's quite easily possible already.

Its not that easy, since it would be one-way only.. one listens and then receives, not at the same time

Lmao… How do you think the rednet functions work? I'd suggest you go do some reading on os.pullEvent, which you would probably have to use for input anyways.
http://computercraft.info/wiki/Os.pullEvent

I think nsh can do what you're looking for. Either that or vncd, depending on how you're wanting it set up.

I'll look at that, thanks, although it would be easier with a peripheral.

Just looked at it, doesn't do what I want, cause I want a completely separate monitor, not remote control or screen sharing

With the right program for incoming connections, it could be used to set up connecting computers as "monitors" or dumb terminals. I'm fairly certain it will do what you want, with a little coding on your part.

just send through all of the events to the remote computer and send all the terminal calls through. you can make 2 programs run at the same time by using co-routines or that multitasking api. on the remote computer just make sure to send all the events to the first computer so yo ucan iteract with it.

wilcomega, on 26 April 2014 - 12:42 PM said:

just send through all of the events to the remote computer and send all the terminal calls through. you can make 2 programs run at the same time by using co-routines or that multitasking api. on the remote computer just make sure to send all the events to the first computer so yo ucan iteract with it.

Not all events. You'd probably want to leave out all except user action events (click, key, char, *maybe* redstone). Other events, like timers, would probably be only necessary for the host.

The events he will want to send through will depend on what code he needs to run. Personally, I think "redstone" events would be useless, as to get anything out of them, you have to check all sides against the redstone api and that quickly becomes a hassle.

awsmazinggenius, on 19 May 2014 - 02:41 PM said:

The events he will want to send through will depend on what code he needs to run. Personally, I think "redstone" events would be useless, as to get anything out of them, you have to check all sides against the redstone api and that quickly becomes a hassle.

Indeed. Oh, also probably want to send terminate events too.

apemanzilla, on 19 May 2014 - 04:58 PM said:

awsmazinggenius, on 19 May 2014 - 02:41 PM said:

The events he will want to send through will depend on what code he needs to run. Personally, I think "redstone" events would be useless, as to get anything out of them, you have to check all sides against the redstone api and that quickly becomes a hassle.

Indeed. Oh, also probably want to send terminate events too.

Well, I just saw this now. I am gonna show this to you how I wanted it to be:

Have a central computer to manage the system(close door, open door, open this, open that) with redstone
Have a file archiving area
Have a rednet processing area
Having a main terminal

Here is where this topic comes onto: The central computer would be directly connected with the other computer, being used like a windows computer on expand mode(on external display). So it processes the key, mouse_click and stuff.