joska wrote:Not really. In that case you'd display the complete application on a remote computer.
What you requested earlier: "display the finished bitmap and send mouse clicks and keypresses back to the server", actually is a high level description of what VNC and RDP protocols do. The RFB (VNC) protocol itself doesn't know anything about applications or windowing systems:http://www.realvnc.com/docs/rfbproto.pdf
But you're partly right, the existing client/server implementations on top of those protocols display complete applications.
joska wrote:I'm talking about offloading the CPU-intensive stuff to another computer, but run the actual application on the local computer.
Web-browsing is the topic of this thread. Offloading to other computer means doing www-rendering remotely and Browser application locally.
I've followed (from afar) Browser implementations on top of Firefox, WebKit and Chromium/Blink web-engines at work. They're really complex pieces of software, doing a good usable browser on top of the already working web-engine takes more than year full time work from several people. A decade or two ago it might have been something that one does as a hobby, but not anymore.
And that would be just the part that does "CPU intensive rendering on other machine". I think it would be much better to use already existing solutions (applications & protocols) for that part.
joska wrote:Displaying something like Chrome on an ST using a remote desktop protocol like RDP or VNC is pointless. Modern applications are not designed to be displayed on such low resolution displays.
Both Chrome and Firefox render the whole application with the browser engine. If you say that they don't work in that low resolution, it means that modern browser engines cannot do that either, and this whole discussion thread is pointless.
320x200 resolution is indeed completely useless resolution for browsing web. Minimum usable is 640x400 monochrome.
If you want to test how well e.g. Chrome works with that, on Linux you can do:
Code: Select all
sudo apt-get install xserver-xephyr chromium
Xephyr :1 -screen 640x400@1 -dpi 96 -nolisten tcp -render mono &
(Xephyr is a X-server-in-an-X-window.)
Looks quite usable, especially if you disable bookmarks bar.
If one modifies a x11 VNC server to convert screen contents to monochrome and modifies the communication with client to be something more efficient, that would be both more generic solution and most likely much less work that doing an Atari Browser application that "just" does CPU intensive rendering on other machine.