kdevelop (4.90.90) on remote display?

[Matthew Woehlke]

On 2015-01-30 13:03, Milian Wolff wrote:
> My take on this topic: I don't think its worth spending time on this. Use VNC 
> or something alike if you *really* want it, but I can't don't see any reason 
> for ever running an IDE from a remote machine. Just share the data, e.g. 
> source contents, over VCS and be done with it. Then you can use the local 
> tools at full performance without any of the issues of either VNC or remote X 
> or ...

Granted the performance is going to be... poor... but there may be
reasons why sharing the source code is not an option:

- Working from home on code that should not be copied to "insecure" home
machine.
- Working on huge code base on client machine with very limited disk space
- Running KDevelop as a different user (ssh -X bob at localhost) due to
file permissions or whatnot (I do this *all the time*; I have such an
instance (4.8) running right now)

Actually, all cases could be solved if KDevelop had a nice way to talk
to a remote file system *and* run the builds (and applications) on the
remote system.

I'm more concerned about Qt applications being non-starter over remote
X. That's going to be really, really painful and make me really annoyed.
Especially as right now the third case works beautifully, even when
running heavy OpenGL applications across X forwarding (of course, being
that the client and server are the same machine, I could imagine this
dodges GL issues that might otherwise pop up).

-- 
Matthew