Linked by Thom Holwerda on Fri 14th Oct 2011 23:12 UTC, submitted by judgen
Features, Office "The LibreOffice media team has passed along some new information about what was revealed at this week's LibreOffice conference. At the Paris conference, experimental versions of LibreOffice for iOS, Android, and for web-browsers were revealed."
Thread beginning with comment 493126
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Broken Promises
by Lennie on Sat 15th Oct 2011 07:15 UTC in reply to "Broken Promises"
Lennie
Member since:
2007-09-22

Looks to me like GTK is the one delivering it ;-)

Reply Parent Score: 7

RE[2]: Broken Promises
by bassbeast on Sun 16th Oct 2011 07:10 in reply to "RE: Broken Promises"
bassbeast Member since:
2007-11-11

Then for all intents and purposes its worthless. If you need a bunch of plugins to make it work? Then it is NOT web based, anymore than some big flash/silverlight/.NET mess is web based. Its a client based app with SOME web elements.

If they truly want to make something web based then it should work with the major browsers, Chrome, Firefox, Opera (I'll give a pass on IE, as you usually have to hack around to get it to work anywhere near a standard) and do so WITHOUT having a bunch of extra crud installed.

Because be honest folks: How many non Linux machines do you think are out there with GTK? Answer: Damned few. This also eliminates schools, libraries, offices, and anywhere where the user isn't allowed to just install whatever they want. Kinda kills the WHOLE POINT of the web don't it? After all if I have to install crud why not just use the native client?

Reply Parent Score: 1

RE[3]: Broken Promises
by Alfman on Sun 16th Oct 2011 07:44 in reply to "RE[2]: Broken Promises"
Alfman Member since:
2011-01-28

bassbeast,

"Then for all intents and purposes its worthless. If you need a bunch of plugins to make it work? Then it is NOT web based, anymore than some big flash/silverlight/.NET mess is web based. Its a client based app with SOME web elements."

Well, I understand your point. However HTML/js absolutely sucks at rasterization and highly interactive interfaces at the pixel level. Technically it can be done, but it absolutely crawls even while pegging the CPU to 100% on a modern computer.


The whole OO interface could be re-implemented on top of HTML object primitives, and would be much cooler in my opinion too. However that doesn't seem to be the goal here, which was merely to project the desktop UI into a web browser.

Reply Parent Score: 2

RE[3]: Broken Promises
by Lennie on Sun 16th Oct 2011 20:25 in reply to "RE[2]: Broken Promises"
Lennie Member since:
2007-09-22

You misunderstood. No plugins are needed.

The GTK-backend is a webserver and runs on a 'server' and you connect with the browser like any other website.

The GTK-backend generated a slightly more optimized VNC-like stream of pixels (as far as I could see).

HTML5 Canvas, WebSocket & JavaScript is used to display it and relay the mouse-over and click events back to the GTK-backend on the server.

So again, no plugins are needed. It works with IE10+ and pretty much all other modern desktop and mobile browsers in the near by future.

The only reason it doesn't work in IE9+ and other last year browsers is because the used to be security problems with the new websocket protocol.

Edited 2011-10-16 20:30 UTC

Reply Parent Score: 3

RE[3]: Broken Promises
by jgfenix on Mon 17th Oct 2011 17:00 in reply to "RE[2]: Broken Promises"
jgfenix Member since:
2006-05-25

It doesn´t require a plugin. The GTK application acts like a web server and renders the whole thing like a canvas element in the browser

Reply Parent Score: 1