Thursday, May 28, 2009

OpenWeb 05/29/2009 (a.m.)

  • "........ Google Native Client, still highly experimental, lets browsers run program modules natively on an x86 processor for higher performance than with Web programming technologies such as JavaScript or Flash that involve more software layers to process and execute the code. But to use it, there's a significant barrier: people must install a browser plug-in. However, Google wants to make the technology more broadly accessible in browsers through new technology coming to HTML, the standard used to build Web pages, and at the Google I/O developer conference Thursday demonstrated its work to make that happen...." Looks to me that Google is attacking the problem of integrating a Chrome browser with x86 desktop metal. Maybe it's the only way to get webkit/Chromium Web Apps on a par with native x86-Windows desktop apps? There is that infamous quote describing the Google v Microsoft challengeto consider: "Google has to replace the MSOffice productivity environment on the desktop "Client" before Microsoft replaces Google apps and services on the "Server". (Same holds true for IBM Lotus Notes - WebSphere on the Server and OpenOffice/Symphony on the desktop client). The quote actually comes from some high level Microsoft document experts, said to have been uttered while under the glaze of legendary Czech Pilsners during a recent ISO meet up in Prague. Looks like there is far more to this quote than meets the eye. I wonder though. Google is looking good. So good that perhaps they are confident enough to take things public - as the events at Google I/O seem to indicate? ~ge~

    tags: html5, html+, webkit, webkit_chromium, x86-Chrome

  • Rick Jellife weighs in on the OpenOffice ODF- MSOffice OpenXML interop embroglio. His take is to focus on Classes of Fidelity, providing us with a comparative table of fidelity categories. I wonder though if this ├╝ber document processing approach is anywhere near consistent with the common sense meaning of interoperability to average end-users? IMHO, end-users interpret "interoperability" to mean that compliant applications can exchange documents without loss of information. "..... In my blog last year Is ODF the new RTF or the new .DOC? Can it be both? Do we need either? I raised the question of whether ODF would replace RTF or DOC. I think this issue has come back with a bang with the release of Office 2007 SP2, and I'd like to give another pointer to it for readers who missed it first time around.... "...... OASIS ODF TC has some kind of conformance and testing wing at work, but it is not at all clear that they will deliver anything in this kind of area. Without targetting these classes, ODF's breezy conformance requirements means that ODF conforment software can deliver vastly different kinds of fidelity, yet still accord to the letter of the law (and, indeed, to the spirit of the ODF spec, which allows so many holes) which will cause frustration all-around....." Ouch!

    tags: odf, ooxml, openxml, interop

  • With Documents To Go for the Google Android platform you get read, write, create and sync support for Word and Excel 2007 (OpenXML formatted) documents, support for receiving and sending attachments through Gmail and other applications (including the free RoadSync Exchange beta client, open password protected files, and view Word documents with track changes so you can see what others have done to your document. ZDNet reviewer Mathew Miller also recommends that people check out the details of the DataViz Intact Technology to see how documents will be handled to maintain file formatting and structure throughout the process of editing. There are two YouTube Video demonstations of "Documents to Go" running on an Android. ........ No collaborative editing with MSOffice desktops, but this is outstanding stuff.

    tags: openxml, dataviz, android


Posted from Diigo. The rest of my favorite links are here.

Post a Comment