Re:Gtk3 on a HTML5 backend
by postfuturist on Tuesday November 23, 2010 @05:46PM
(#1935689)
Browsers exist in more places than X clients.
Getting X tunneled over HTTP is actually pretty complicated:
* The client/server thing is reversed * X expects everything to be fully asynchronous (WebSockets get a lot of hype but they're pretty useless at this stage IMO) * XRender is a big mismatch to canvas drawing API (the old X drawing protocol is in some ways better, in many ways (esp. color) much worse)
Isn't this the sort of thing X was built for? Client rendering, but the underlying app in a remote server? How is rendering this in the browser more useful/cool?
(edit: typo)