This is a read-only snapshot of the ComputerCraft forums,
taken in April 2020.
Make the computer a monitor
Started by Jummit, 24 September 2018 - 02:32 PMPosted 24 September 2018 - 04:32 PM
The Idea is simple: Your computers front display becomes a monitor. Its not very large, but you can do some nifty stuff with it, like displaying cool screen savers or something. It is simply used like any peripheral, you can wrap it using peripheral.wrap("front"). This removes the ability to interact with peripherals in front of the computer, but that doesn't make a lot of sense anyway, because how would a computers connect to something by its screen?
Posted 25 September 2018 - 12:03 AM
If you REALLY want the computer to be a monitor, just get a peripheral mod with keyboards, connect your computer to a screen, then pair the keyboard. Wah-lah,
Posted 25 September 2018 - 02:38 AM
Posted 25 September 2018 - 11:23 AM
But it doesn't make sense. You have this computer with a screen that shows a command prompt, but it acts like a tower computer; You have to connect a screen to it.If you REALLY want the computer to be a monitor, just get a peripheral mod with keyboards, connect your computer to a screen, then pair the keyboard. Wah-lah,
Posted 25 September 2018 - 01:09 PM
Honestly, I feel the best solution here would be to go the OpenComputers route and just display the computer's terminal on the front as well. This means you don't need to have a whole separate peripheral, and IMO makes sense thematically.
Truth be told, this wouldn't be too hard to implement (given that it'd be largely an adaption of monitor rendering code), but it does raise the question about how to handle the wildly different aspect ratios of the actual terminal and the block's screeen (see this PR for an example of a similar issue).
Truth be told, this wouldn't be too hard to implement (given that it'd be largely an adaption of monitor rendering code), but it does raise the question about how to handle the wildly different aspect ratios of the actual terminal and the block's screeen (see this PR for an example of a similar issue).
Edited on 25 September 2018 - 11:09 AM
Posted 25 September 2018 - 07:29 PM
But the oversized blinking command prompt is kind of computercrafts trademark :)/>, but showing a minitature version of the screen would remove that…
Edited on 26 September 2018 - 09:35 AM
Posted 26 September 2018 - 06:28 AM
But it doesn't make sense. You have this computer with a screen that shows a command prompt, but it acts like a tower computer; You have to connect a screen to it.
You don't "have to connect" a screen to a computer block. You simply have to open its GUI, same as with most all other interactive blocks. Complaining about this is akin to complaining that items placed on crafting benches aren't visible in "the world" - but pretty much everything in Minecraft is stylised in this way.
That leaves only practical concerns, such as "what would this let you do that you can't do already": and to my mind the answer is "nothing", as dedicated monitor blocks not only allow exactly what you're asking for, but they also handle direct touch input without the need for a GUI at all.
Honestly, I feel the best solution here would be to go the OpenComputers route and just display the computer's terminal on the front as well. This means you don't need to have a whole separate peripheral, and IMO makes sense thematically.
I haven't played with OC all that much, but isn't their approach "peripheral only"? You either place a separate monitor block next to your computer, or you don't have display output at all.
Posted 26 September 2018 - 09:20 AM
Yes, though the model of interaction is relatively similar to CC - you still right click on it to type, etc… I guess my argument was more on the aesthetic being similar.I haven't played with OC all that much, but isn't their approach "peripheral only"? You either place a separate monitor block next to your computer, or you don't have display output at all.
This is definitely true. I'd argue it'd look jolly cool, but I'm really not sure it's worth the additional implementation costs and network/render overhead.That leaves only practical concerns, such as "what would this let you do that you can't do already": and to my mind the answer is "nothing"