Phil Spiegel said:
I did say 'or equivalent '
.. whatever the 'modern' equivalent is, unless its to waste memory like windows.
I look forward to reading documentation telling me what graphics, to match BBC BASIC /RISCOS drawing commands I can use. I'm not a 'games player'
- flight sim being the only game I've bought and played in over 10 years -but that's modelling of the 'real world' - sort of, with the Healt&Safety aspect to extreme
My initial project is for far simpler screen displays monitoring trains passing.
The screen "modes" have been posted before, but essentially the R-Pi will support almost any resolution that a modern montor will support, right up to 1920x1080 in full colour.
As for the graphics, that will be up to the application or programming language you pick for your applicaiton. How does it get inputs, how do you want to represent outputs?
So I hope this doesn't come as a shock to you when I say that there are no built-in graphics commands! There are no peek/poke/VDU/plot and line or *fx commands.
Unless you want to write really low-level code, then you need to use a program or libary to manage it all for you and (arguably) the easiest way to get pixels onto the screen is with the SDL library, but you can build on top of that with other things. My BASIC uses SDL, so in BASIC, I can
colour = Green
line (0,0, 100,100)
for example, and behind that is a C program doing the hard work, by using the SDL (Simple Direct media Layer) library which then interfaces to the hardware via the operating system (Linux) the SDL library really only provides me with a block of RAM that represents the screen - I have to draw that line, pixel by pixel in a piece of C... (Using Bressenhams algorithm) If you want to see some of my graphics commands, then click on: http://unicorn.drogon.net/rtb3.png
SDL is callable from many systems - I use C, but if you wanted to code in Python, then there is a Python library for it too.
But if you want to do "windows" then it gets somewhat more complex, but also at a higher level, so once you've got the thing initialised, then it boils down to "open window", then you dress it with icons, buttons, tabs and so on - more code to write, but the interface is also at a higher level.
And you could even use a web browser as your output device - so if you can read your inputs (trains passing by) from a PHP or Python program, then you could have those programs output HTML - then run a web server on the R-Pi, and a web browser and off you go. Advantage then is that you could see your captured data from anywhere in the world as long as you have an Internet connection into it. Web browser to Server is a very high level protocol indeed, but it's used rather a lot as it can be realtively easy to get something in a graphical form to allow user inputs to stuff running behind the scenes. If you want an example of using a web browser to view external sensors, then have a look at this: http://www.dartcom.co.uk/weath...../index.php
(not my site, but a good example) or even (more approriate for you): http://www.landsendweather.info/ais
(again, not one of my sites, but it's run by a friend)
So maybe start thinking at a little bit of higher level and not wory (too much) about wasting memory - at least for now!