Develop on-device [Was: Re: [fpc-devel] "embedded" again]

[Mark Morgan Lloyd]

Michael Schnell wrote:
> On 01/15/2013 12:01 PM, Thomas Schatzl wrote:
>> Do it on the device. Either directly or remote via NX, VNC or even
>> X-forwarding is fast enough on current devices.
> As on the QNAP there is no graphics hardware, VNC will not work (at 
> least not out of the box). It needs a Frame buffer RAM and if there is 
> none to install X on, you need to do a simulated Framebuffer RAM in the 
> normal RAM. I suppose this is possible, but might slow down things a lot 
> (see RPi with hardware-shared FB RAM). X-forwarding is rather "funny", 
> the X-Terminal being the X-Server for the device. So the best choice is NX.

I'm sorry, but I believe that's misleading. I was routinely able to run 
the server-end of VNC (i.e. the code that runs on the same machine as 
the app) on a Slug, on X-based systems it simulates an X server so 
doesn't need a frame buffer etc. Simulated framebuffers are noting new: 
Xnest does exactly that, and there's also a standard dummy which is most 
often used to allow a display manager (gdm or whatever) to run headless.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]