Group items tagged

We can all learn a lot of lessons from the history of DDE/OLE/ OLE3/COM /ActiveX/DCOM /COM+ (you can start reading up on Wikipedia to get some background) and how we went from everyone using best-of-breed standalone apps to one integrated, nearly monolithic Office. It basically all started with copy and paste. People who never spent a lot of time in singletasking, character-mode operating environments like the DOS command line don't recall that simply copying-and-pasting information between apps was difficult at the time. And part of the revelation of Windows for mainstream users (or Mac, for leading-edge tech fans), was being able to easily share data in that way. This was different than what Unix users were used to with the command-line pipe, or from what most applications do with feeds today, in allowing structured information flows between applications. There's a desire to combine data from different sources in an arbitrary way, and to have the user interface display the appropriate tools for whatever context you're in. The dominant model here, probably because of the influence of the early PARC demos, is to have toolbars or UI widgets change depending on what kind of content you're manipulating. Microsoft was really into this in the early 90s with OLE2, where your Word toolbars would morph into Excel toolbars if you double-clicked on an embedded spreadsheet. It was ungainly and ugly and slow, especially if you had less than an exorbitant 8MB of RAM, but the idea was pretty cool. And it still is. People are so focused on data formats and feeds that they're ignoring consensus around UI interoperability. The Atom API and Metaweblog API give me a good-enough interface if I want to treat a discrete chunk of information (like a blog post) as an undifferentiated blob. But all the erstwhile spec work around microformats and structured blogging (I forget which one is for XML and which one's for XHTML) doesn't seem to have addressed user experience or editing behavior

The demo movie above from Adobe shows off some WebKit-based experiments that seek to change that. Adobe Engineering VP Paul Betlem narrates and the demo, and he shows how his team is extending the WebKit browser to do some new typographic tricks. WebKit is the open source engine behind Safari and Google Chrome, and it powers the most popular mobile browsers like the ones on the iPhone, iPad, iPod and all the Android phones. The demo certainly shows some impressive results. However, we're a bit suspicious of the methodology behind the results. Betlem talks about extending WebKit's CSS support via vendor prefixes, but neglects to mention what those prefixes are built against - in other words, there's no mention of submitting a standard that other browsers could work from.

A little tidbit from the Microsoft gathering this evening.  While demonstrating Outlook for Mac and the HTML rendering engine, Microsoft employees revealed that instead of using the Word HTML rendering that previous versions of Mac Office used (and the PC version as well), Microsoft has moved over to Apple's Webkit rendering engine to render HTML mails.  Outlook 2011 also uses WebKit to create HTML mail. For those of you who didn't like Entourage's HTML mail, Outlook's WebKit mail, you are in for a pleasant surprise. Why is this a big deal?  This is the first time that Microsoft has used Apple's Open Source Webkit framework in their products.  It will be interesting to see if Webkit spreads to other areas. Office 2011 ships tomorrow and starts at $110 for a 2 license student edition.

Google has been making a number of acquisitions that are clearly Docs-related. Over the weekend, TechCrunch reported that the search giant is in the final stages of talks to acquire DocVerse, a startup that lets users collaborate around Office documents, for $25 million. The deal would also bring Google some key hires, since the startup's co-founders were managers on SharePoint, Microsoft's popular collaboration service. This follows the November acquisition of AppJet, a company founded by former Googlers that created a collaborative word processor. (It's worth noting that Google Docs itself was the offspring of several acquisitions, including Google's purchase of Writely.) Meanwhile, Google has been talking up the splash it wants Google Docs to make in 2010. Don Dodge, who just made the move from Microsoft to Google, recently told me, "2010 is going to be the year of Gmail and Google Docs and Google Apps." Even more concretely, Enterprise President Dave Girouard said last month that Docs will see 30 to 50 improvements over the next year, at which point big companies will be able to "get rid of Office if they choose to." Presumably features from AppJet and DocVerse will be among those improvements. I'd certainly be thrilled to see the battle between Office Docs become a real competition, rather than upstart Google slowly chipping away at Microsoft's Office behemoth.

EU settlement will alter Microsoft's stance on interoperability By Kurt Mackie Dec 21, 2009 Microsoft provided more details about its settlement with the European Commission (EC), particularly with regard to interoperability agreements. In a blog post on Thursday, Dave Heiner, Microsoft's vice president and deputy general counsel, claimed that the company has pledged to implement a threefold approach to interoperability that EC Commissioner Neelie Kroes outlined in past speeches. Heiner summarized that approach: companies should disclose technical information, provide a remedy if the information is inadequate and charge equitable royalty rates for associated intellectual property. Kroes had also specifically called for companies to follow open standards as one of the best ways to achieve interoperability. However, Heiner omitted the word, "open," from his comment. He said that "products from different firms can work well together when they implement common, well-designed industry standards." Microsoft's interoperability pledge announced this week appears to continue ideas the company put forth in February 2008. At that time, the company announced broad interoperability principles as well as APIs for software developers working with Microsoft's mainline products, including Windows client and server operating systems, Exchange, Office and SharePoint, among others. Microsoft has been releasing documentation for that purpose, with "hundreds of Microsoft developers" devoted to the effort, according to Heiner. The new elements to Microsoft's interoperability pledge appear to be warranty and patent-sharing templates. Those documents, and more, can be accessed at the end of a statement about the settlement by Brad Smith, Microsoft's senior vice president and general counsel.

Microsoft's free "Office Starter" suite will be able to fully open and display complex OOXML - 2010 MSOffice documents.  But they will not be able to execute macros or edit embedded logic such as Scripts, Macros, OLE, and ODBC connectors.  That's a killer for workgroup-workflow oriented business documents.  A category of "compound documents that includes forms, reports, compound documents and workflow logic. As for what users can do with the applications, Capossela said that Word will be capable of opening and displaying even the most complex documents. However, Office Starter users won't be able to use macros, create automated tables of contents, or add comments, though they will see comments added by others. The approach with Excel is similar, with users able to view and edit documents, but not create their own pivot tables and pivot charts, for example.

This week Microsoft will take its Office 2010 suite out of beta. If you're considering upgrading Office with Office, we'd encourage you to consider an alternative: upgrading Office with Google Docs. If you choose this path, upgrade means what it's supposed to mean: effortless, affordable, and delivering a remarkable increase in employee productivity. This is a refreshing alternative to the expensive and laborious upgrades to which IT professionals have become accustomed. Google Docs has been providing rich real-time collaboration to millions of users for nearly four years. It lets employees edit and share documents, spreadsheets, and presentations in the browser from anywhere in the world. We recently made tremendous strides in improving Google Docs formatting, speed and functionality, and a growing number of companies are now using it as their primary productivity software. Of course, you probably already own Office 2003 or 2007 (or maybe Office 2000?), and there's no need to uninstall them. Fortunately, Google Docs also makes Office 2003 and 2007 better. For example, you can store any file - including Microsoft Office documents - in Google's cloud and share them in their original format (protected, naturally by Google's synchronous replication across datacenters). Plus, in the coming months, Google will enable real-time collaboration directly in Office 2003 and 2007, as you can see here. Google Docs represents a real alternative for companies: a chance to get the collaboration features you need today and end the endless cycle of "upgrades". For more information on the choices available to you, check out the summary below. But don't take our word for it - you can try Google Docs and the rest of the Google Apps suite for free. The only thing you have to lose is a server or two.

With Office 2010 already available to corporations, documents you can't quite open in Office 2007 are soon to appear in your inbox. If you're not upgrading, or never use Office anyways, TextMaker Viewer is a light, snappy document viewing option. TextMaker Viewer actually opens a huge range of word processing files, including Office, OpenOffice.org, the TextMaker app this viewer derives from, and all the standard low-tech formats like HTML, TXT, and RTF. Microsoft offers its own viewers, but only the PowerPoint Viewer has made it up to 2010 compatibility so far. Beyond that, TextMaker is a very lightweight application, so opening huge files likely won't choke up your system as thoroughly. TextMaker Viewer 2010 is a free download for Windows systems only. There does seem to be an issue with registering the free version to turn off the "nag" screen on launching, but after a few starts, a checkbox to hide that screen does appear.

1)  What's the Best Android Phone for Verizon Right Now? Droid X. This was one of two reviews to break into the top 10, both of them on Android. It hit as the Android frenzy was reaching a crescendo and highlighted how a bigger screen could work on smartphones. This review and the number two post also hit the top mobile posts of the year. 2)  Android Sales Overtake iPhone. This has been a theme that has generated a lot of traffic all year. With Android ascendant, we saw the first quarter where recent sales surged past the iPhone. While the iPhone appears to still have a larger overall installed base, the reports of Android's rise touched off a lot of debate about where the two platforms will end up. 3)  Nexus One: The Best Android Phone Yet. This post went up in January and foreshadowed a big year for Android. While praising the device, Om said it still didn't match the experience of the iPhone, but it showed Google was ready to compete. 4)  4chan Decides to Do Something Nice for a Change. This was a nice change-up and showed that 4chan, despite its reputation for sophomoric humor and sexual imagery, could be used for good. The online community banded together to wish 90-year-old WWII veteran William J. Lashua a happy birthday. 5)  Your Mom's Guide to Those Facebook Changes and How to Block Them. Where would we be without a Facebook post in our top 10? This post looked at the expansion of the "like" button to outside websites and instant personalization and explained how users can sidestep the features. This fit into a larger story about privacy on Facebook, which never seems to get old. 6)  Is Apple About to Cut Out the Carriers? This post stirred a lot of conversation after we reported that Apple was looking at putting its own SIM card in iPhones to sell devices directly to consumers. The move would have allowed Apple to cut out European carriers. It looks like the plan didn't come to pass, but it illustrated the power of Apple and its am

If this doesn't make Florian weep, nothing can! Google Cloud Connect for Microsoft Office is now available worldwide. This plugin for Microsoft Office is available to anyone with a Google Account, and brings multi-person collaboration to the Microsoft Word, Excel and PowerPoint applications that you may still need from time to time. The plugin syncs your work through Google's cloud, so everyone can contribute to the same version of a file at the same time. Learning the benefits of web-powered collaboration will help more people make a faster transition to 100% web collaboration tools.

the online document service Crocodoc, which Thursday wrote about last year, is rolling out some new features that should make it easier to collaborate on and mark up highly-formatted documents, including PDFs, Microsoft Word and PowerPoint documents, and PNG and JPEG images.  Crocodoc is out to replace Adobe Acrobat as the preferred way to display, view and mark up highly-formatted documents.

Neil McAllister provides an in-depth no-holds-barred comparison of Google, Zoho and Micorsoft Web Office Productivity Apps.  It's not pretty, but spot on honest.  Some of the short comings are that Neil overly focuses on document fidelity, but is comparatively light on the productivity environment/platform problems of embedded business logic.  These document aspects are represented by internal application and platform specific components such as OLE, scripting, macros, formulas, security settings, data bindings, media/graphics, applications specific settings, workflow logic, and other ecosystem entanglements so common to MSOffice compound "in-process" business documents.   Sadly, Neil also misses the larger issue that Microsoft is moving the legacy MSOffice Productivity Environment to a MS-Web center.   excerpt:  A spreadsheet in your browser? A word processor on the Web? These days, SaaS (software as a service) is all the rage, and the success of Web-based upstarts like Salesforce.com has sent vendors searching for ever more categories of software to bring online. If you believe Google, virtually all software will be Web-based soon -- and as if to prove it, Google now offers a complete suite of office productivity applications that run in your browser. Google isn't the only one. A number of competitors are readying Web-based office suites of their own -- most prominently Zoho, but even Microsoft is getting in on the act. In addition to the typical features of desktop productivity suites, each offering promises greater integration with the Web, including collaboration and publishing features not available with traditional apps.

The ripples from the European Commission v. Microsoft decision continue to flow. The catch, of course, is that the patent rights will almost certainly be subject to the Microsoft Open Specification Promise, a weasel-worded document that actually grants no rights. http://law.bepress.com/unswwps/flrps/art71/ But someone with some clout will push that issue sooner or later.

Conrado gets a very good review! Excerpt: Feng Office packs most of the features you should require for most project management duties. In addition to basics like calendars, contacts and email, it also provides milestone and task management, and a built-in time-tracking function. All of the above are well-implemented, although some users may actually find the similar interface design of all the functions more confusing than helpful, since it's often not clear which function you're using at any given time without looking at what tab is highlighted. I like the uniformity, though, since it gives each feature a sense of connectedness to the others and adds to the feeling that Feng Office is a holistic solution. Notes, Links and Documents features also bring much to Feng Office's overall value proposition, and each is well-executed. You can even create new Word docs and PowerPoint HTML documents and presentations directly from within Feng Office using its own built-in editors, both of which retain UI elements from Microsoft's own suite. That means less time switching from browser to standalone apps, which adds up to better productivity.

Digital Daily is carrying John Paczkowski's point-by-point twitter stream of the Google Apps Event. Fascinating stuff. Especially Dave Girouard's comments comparing Google Apps to MSOffice. One highlight of the event seems to be the announcement of a Google OutLook integration app. Sounds like something similar to what Zimbra did a few years ago prior to the $350 million acquisition by Yahoo! Zimbra perfected an integration into desktop Outlook comparable to the Exchange - Outlook channel. If Google Apps Sync for Outlook integration is a s good as the event demo, they would still have to crack into MSOffice to compete with the MSOffice-SharePoint-MOSS integration channel. Some interesting comments from Google Enterprise customers, Genentech, Morgans Hotel Group, and Avago ....... At an event in San Francisco, Google is expected to discuss the future of its productivity suite and some enhancements that may begin to close the gap with Microsoft (MSFT) Office, something the company desperately needs to do if it wants to make deeper inroads in the enterprise area. As Girouard himself admitted last week, Apps still has a ways to go. "Gmail is really the best email application in the world for consumers or business users, and we can prove that very well," he said. "Calendar is also very good, and probably almost at the level of Gmail. But the word processing, spreadsheets and other products are much less mature. They're a couple of years old at the most, and we still have a lot of work to do."

Summary: Collaborative document editing means multiple editors being able to edit a shared document at the same time.. Live and concurrent means being able to see the changes another person is making, keystroke by keystroke. Currently, there are already a number of products on the market that offer collaborative document editing. Some offer live concurrent editing, such as EtherPad and SubEthaEdit, but do not offer rich text. There are others that offer rich text, such as Google Docs, but do not offer a seamless live concurrent editing experience, as merge failures can occur. Wave stands as a solution that offers both live concurrent editing and rich text document support.  The result is that Wave allows for a very engaging conversation where you can see what the other person is typing, character by character much like how you would converse in a cafe. This is very much like instant messaging except you can see what the other person is typing, live. Wave also allows for a more productive collaborative document editing experience, where people don't have to worry about stepping on each others toes and still use common word processor functionalities such as bold, italics, bullet points, and headings. Wave is more than just rich text documents. In fact, Wave's core technology allows live concurrent modifications of XML documents which can be used to represent any structured content including system data that is shared between clients and backend systems. To achieve these goals, Wave uses a concurrency control system based on Operational Transformation.

Surprise-to make more money! After the initial burst of discussion about Google putting their toe into the standardized metadata water, I started wondering about the corner of the pool they had chosen. They're not ready to start parsing any old RDFa; they'll be looking for RDFa that uses the vocabulary they somewhat hastily defined for the purpose. Why does the vocabulary define the properties that it defines? It will be interesting to see how the big hustling SEO world adapts to this. In the words of Drupal project lead Dries Buytaert, Structured data is the new search engine optimization. When he writes "Every webmaster wanting to improve click-through rates, reduce bounce rates, and improve conversation rates, can no longer ignore RDFa or Microformats", it reminds me that when the SEO world eventually gravitates more in the RDFa direction or the microformats direction, these very quantitative, results-driven people will have some real data to explain why. I'll have to start searching their voluminous discussions out there to see what people are saying.