Group items tagged

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.

Interesting stats coming out from the recent Forrester study on Office Productivity.  The study was conducted by Philipp Karcher, and it shows a fcoming collision of two interesting phenomenon that cannot continue to "coexist".  Something has to give. The two phenom are the continuing dominance and use of client/server desktop productivity application anchor, MSOffice, and, the continuing push of all business productivity application to highly mobile cloud-computing platforms.   It seems we are stuck in this truly odd dichotomy where the desktop MSOffice compound document model continues to dominate business productivity processes, yet those same users are spending ever more time mobile and in the cloud.  Something has got to give. And yes, I am very concerned about the fact that neither of the native XML document formats {used by MSOffice (OXML), OpenOffice and LibreOffice (ODF)} are designed for highly mobile cloud-computing.   It's been said before, the Web is the future of computing.  And HTML5 is the language of the Web.  HTML is also the most prolific compound-document format ever.  One of the key problems for cloud-computing is the lack of HTML5 ready Office Productivity Suites that can also manage the complexities of integrating cloud-ready data streams. Sadly, when Office Productivity formats went down the rat hole of a 1995 client/server compound document model, the productivity suites went right with them.  Very sad.  But the gaping hole in cloud-computing is going to be filled.  One way or the other.

Good stuff!  Be sure to watch the YouTube video.  There is a demo of how a Google Docs and MSWord collaborative document gets synchronized.  Notice the layout mismatch.  They do however seem to understand the problems of the advanced formatting common to compound documents and "in-process" workgroup documents. excerpt:  OffiSync is launching an all-new version of its Microsoft Office to Google Docs synchronization tool, a plugin that's a "must-have" for anyone still straddling the two worlds of office suites: that is, the desktop-based world of Microsoft software and the web-based world of Google Docs. In the updated version of OffiSync, set to arrive minutes from now, you'll be able to co-author documents in real-time between Microsoft Office and Google Docs, no matter what version of the Office software you use. There are a few other new features too, including improvements to search, added Google Sites support and the ability to store any file type, but it's the co-authoring feature that's today's biggest reveal.

Finally! Someone who gets it. For an office suite to be considered as an alternative to MSOffice, it must be designed with multiple levels of compatibility. It's not just that the "feature sets" that must be comparable. The guts of the suite must be compatible at both the file format level, and the environment level. Randall put's it this way; "It's the ecosystem stupid". The reason ODF failed in Massachusetts is that neither OpenOffice nor OpenOffice ODF are designed to be compatible with legacy and existing MSOffice applications, binary formats, and, the MSOffice productivity environment. Instead, OOo and OOo-ODF are designed to be competitively comparable. As an alternative to MSOffice, OpenOffice and OpenOffice ODF cannot fit into existing MSOffice workgroups and producitivity environments. Because it s was not designed to be compatible, OOo demands that the environment be replaced, rebuilt and re-engineered. Making OOo and OOo-ODF costly and disruptive to critical day-to-day business processes. The lesson of Massachusetts is simple; compatibility matters. Conversion of workgroup/workflow documents from the MSOffice productivity environment to OpenOffice ODF will break those documents at two levels: fidelity and embedded "ecosystem" logic. Fidelity is what most end-users point to since that's the aspect of the document conversion they can see. However, it's what they can't see that is the show stopper. The hidden side of workgroup/workflow documents is embedded logic that includes scripts, macros, formulas, OLE, data bindings, security settings, application specific settings, and productivity environment settings. Breaks these aspects of the document, and you stop important business processes bound to the MSOffice productivity environment. There is no such thing as an OpenOffice productivity environment designed to be a compatible alternative to the MSOffice productivity environment. Another lesson from Massach

Nice article from Scott M. Fulton describing Microsoft's iron fisted lock on government desktop productivity systems and the great transition to a Cloud Productivity Platform.  Keep in mind that in 2005, Massachusetts tried to do the same thing with their SOA effort.  Then Governor Romney put over $1 M into a beta test that produced the now infamous 300 page report written by Sam Hiser.  The details of this test resulted in the even more infamous da Vinci ODF plug-in for Microsoft Office desktops.   The lessons of Massachusetts are simple enough; it's not the formats or office suite applications.  It's the business process!  Conversion of documents not only breaks the document.  It also breaks the embedded "business process". The mystery here is that Microsoft owns the client side of client/server computing.  Compound documents, loaded with intertwined OLE, ODBC, ActiveX, and other embedded protocols and interface dependencies connecting data sources with work flow, are the fuel of these client/server business productivity systems.  Break a compound document and you break the business process.   Even though Massachusetts workers were wonderfully enthusiastic and supportive of an SOA based infrastructure that would include Linux servers and desktops as well as OSS productivity applications, at the end of the day it's all about getting the work done.  Breaking the business process turned out to be a show stopper. Cloud Computing changes all that.  The reason is that the Cloud is rapidly replacing client/server as the target architecture for new productivity developments; including data centers and transaction processing systems.  There are many reasons for the great transition, but IMHO the most important is that the Web combines communications with content, data, and collaborative computing.   Anyone who ever worked with the Microsoft desktop productivity environment knows that the desktop sucks as a communication device.  There was

Office suites are now taking the cloud route and offering advanced services, luring partners with smart gain  By Varun Aggarwal While all applications are moving to the cloud, there is no reason why the ubiquitous office productivity suites like MS Office or OpenOffice should stick to the desktop. Providing customers with a key set of capabilities, and a browser to aid easy access makes complete sense. Take for instance a student working on a class paper. Writing in a Web browser might aid in sharing and incorporating constructive changes, but it is a cumbersome experience as compared to using Office on his PC. But by using productivity suite online, he gets best of both worlds.  

Collaborate and Edit documents with Zoho, Store and Manage in Microsoft® SharePoint®. Zoho is onto something here. The video is well worth the watching. Anthony Ha of Venture Beat ahd this to say: "As online office software tries to move into big corporations, it's starting to work more closely with entrenched solutions - which often means technology built by Microsoft. In the latest example, Zoho just announced plans to offer its collaboration services as an add-on for SharePoint, Microsoft's server and software for collaboration and document management." "Basically, that means you can use Zoho Office as the interface for collaborative editing of documents, while the documents themselves sit safely on the SharePoint server, behind the corporate firewall. The add-on brings a more web-like interface to SharePoint; rather than having to check documents in and out as they work on them, multiple users can jump into a document and edit it at once, and also send instant messages back-and-forth within their application using Zoho Chat." "This is a smart way to get Zoho into companies that wouldn't consider making the full jump into online office applications, but want to experiment with these kinds of tools without sacrificing security or throwing away existing hardware. The financial investment is small, too - a 30-day trial period, followed by $2 per user per month if companies pay for a year, or $3 per user per month if companies pay by month."

Custom Document Format Interoperability You may have heard that Office 2007 SP2 will now support editing files in the OpenDocument 1.1 (ODF) format. This document format was added to Office's long list of supported documents formats to give customers more choices for the format they use to save their documents. In addition to allowing you to edit the ODF 1.1 format within Office 2007, SP2 also supports a new External File Format API that can be used to edit other document formats as well. With this API, users can choose to save their documents in any format they want. In this post we will explore how to use the API to enable Office 2007 to edit our own custom document format. We will then use Office 2007 to save our custom format as DOCX, ODT and HTML. Our Custom Document Format For the purpose of this article, we have a company who needs to manage their sales pipeline information. The data is available as XML, but they do not want to spend the money to build a custom editor. They just want to let their users edit the pipeline data in Word, as a table. They give these files an extension of SPLX (i.e. Sales PipeLine Xml) The sales pipeline information is made up of a series of SalesItem tags, each with a unique id that represents the index of the item. They track the name of the customer (CustomerName), how much the deal represents (DealValue) and a percent that represents how confident they are that the sales opportunity will close (ConfidencePercent).

Interesting article describing a recent press conference where Microsoft introduced their latest SkyDrive alternative to Apple's iCloud initiative.  Having had considerable experience with SkyDrive and the entire "sync-share-store" Cloud category, I left a lengthy comment. Computerworld - Microsoft is pitching its SkyDrive online storage service to Office for Mac users, calling Apple's iCloud offering "not enough" for collaboration, file sharing and anywhere-access to documents. Microsoft released an OS X SkyDrive client preview two weeks ago, adding Macs to the list of devices -- Windows, particularly the upcoming Windows 8, iOS and Windows Phone -- with native support for the Dropbox-like service. On Monday, the Redmond, Wash. developer stumped for SkyDrive on its Office for Mac website. "With the SkyDrive for Mac OS X Lion preview, SkyDrive for Windows, and the release of SkyDrive for iPad, you can save and store your important documents or other files in the SkyDrive folder in Finder and access them from anywhere," the Office for Mac team wrote on its blog.

Notification of this article also appeared in the Diigo Document Wars Group..... WebODF...   An especially interesting project that was presented is WebODF, which wants to bring ODF to the web. Jos van den Oever started from the observation that a lot of office suites are moving into the "cloud". Examples are Microsoft Live Office, Google Docs, and Zoho. But where are the free software alternatives for the cloud? For OpenOffice.org, KOffice, AbiWord, and Gnumeric, there are none that have a cloud version with ODF support. That was the motivation for Jos to start a project to fill in this gap and let users view and edit ODF documents on the web without losing control of the document into some company's servers. The strategy Jos followed was to use just HTML and JavaScript for the web application. The application then loads the XML stream of the ODF document as is into the HTML document and puts it into the DOM tree. Styling is done by applying CSS rules that are directly derived from the and elements in the ODF document. That is how WebODF was born; it is a project with the initial goal of creating a simple ODF viewer and editor for offline and online use, implemented in HTML5. The small code base consists of one HTML5 file and eight JavaScript files, each of which is a few hundred lines of code. The most interesting part is that it doesn't need server-side code execution: the JavaScript code is executed in the user's browser and saving the document to the web server is done using WebDAV. It supports both the Gecko and WebKit HTML engines. There is also an implementation on top of QtWebKit, which is for better desktop integration, and an ODFKit implementation. This means that WebODF is an easy way to add ODF support to almost any application, be it in HTML, Gtk, or QML. KO GmbH has received funding from NLnet to improve the current WebODF prototype and see how far the idea goes. Interested readers can try the online demo

The Barcelona World Mobility Conference is under way, and Microsoft is making a show of force.  They are hitting with features that support both "Social Network Hubs" (People Hub) and "Productivity Hubs" (Office Hub).  The key to Microsoft's Windows 7 Smartphone success is not that of new and exciting features competitive with Apple and Google smartphones.  No, the key feature that Microsoft owns is that of integration into legacy desktop productivity business systems based on the MSOffice productivity platform, and, more importantly, integration into the emerging Web centered but proprietary Microsoft Business Productivity Platform.  Stay tuned. excerpt on the new Windows 7 feature set:  The Office Hub lets you easily sync your documents between your phone and your PC. Office Hub comes with OneNote, for notetaking, Documents and Sharepoint for presentation collaboration. Users will also have access to an Outlook Mail application which gives similar features, like flagging important e-mails, that you'd find on the desktop version.

What a dumb ass statement: "That's certainly one reason Microsoft still holds a giant lead in market share." The SFGate article compares Google Apps lack of service to Microsoft's Productivity monopoly, suggesting that Microsoft provides better service?  That's idocy.  Microsoft's service is non existent.  Third party MSDN developers and service businesses provide near 100% of MS Productivity support.  And always have.   Where Microsoft does provide outstanding support is to their MSDN network of developers and service providers.   Google will have to match that support if Google Apps is to make a credible run at Microsoft.  But there is no doubt that the monopolist iron grip on the desktop productivity platform is an almost impossible barrier for Google to climb over.  Service excellence or not.

Gartner Analyst Michael Silver wrote the study, "Windows 7 is all but inevitable".  Here is a quote explaining why it's near impossible to migrate away from MSOffice and the MSOffice Productivity Environment: There have been many organizations that have investigated moving off Microsoft Office, usually to a distribution of OpenOffice.org (including the free download, Sun's StarOffice, Novell Edition and IBM Symphony), but relatively few have actually made the migration. Impediments include switching costs, issues with macros, stationery, databases and mail clients. For better or worse, for the past 15 years, organizations have chosen to overprovision and deploy a product that can do everything the most-advanced user requires to every user for the sake of homogeneity. Organizations that want to deploy OpenOffice.org (OO.o) need to come to terms with the fact that some users will still require MS Office and they will be forced to support a mix of products. To Gartner, it makes sense to take advantage of viable perpetual licenses for Microsoft Office for as long as possible. The expensive product you already own will be cheaper than the cheap or "free" product you need to spend money to which to migrate.

Über technologist Michael Hickens writes about the recent Cisco announcement that they intend on competing with Google, Zoho and MOSS in the cloud collaboration space. I left a lengthy comment on this page, trying to come to grips with the meaning of this challenge. I titled my comment, "Cisco Office? Maybe they should consider Feng Office-in-the-Cloud". Good luck Conrado. Go get them. Interestingly, Jason Harrop and i met Ms. Alex Hadden-Boyd, director of marketing for the collaboration software group at Cisco. She was kind enough to refer me directly to David Knight, the technology director of Cisco's WebEX Conferencing initiative. Alex is quoted in a CNet article at: http://news.cnet.com/8301-1001_3-10276549-92.html Cisco is striving to redefine itself as a vendor connecting inner and outer clouds, thus reasserting its relevance in the context of a fluid Web-driven IT world increasingly dominated by the likes of Google, Salesforce, Oracle and IBM. It also hopes to parlay its legacy of infrastructure expertise into a reassuring presence, particularly for veteran IT administrators struggling to balance their in-house infrastructures against the cost-savings and potential efficiencies of cloud computing.

Microsoft has announced the next generation of MSOffice, and it turns out to be SharePoint at the center of the deep connected MSOffice "rich client" desktop productivity environment, and, an online Web version of MSOffice. Who would have guessed that one of the key features to MOSS would be universal accessibility to and collaboration on MSOffice documents - without loss of fidelity? No doubt the embedded logic that drive BBP's (Bound Business Processes) is also perfectly preserved. Excerpt: "Office Web Applications, the online companion to Word, Excel, PowerPoint and OneNote applications, allow you to access documents from anywhere. You can even simultaneously share and work on documents with others online," Microsoft says on its Office 2010 Technical Preview site. "View documents across PCs, mobile phones, and the Web without compromising document fidelity. Create new documents and do basic editing using the familiar Office interface."

One of the "Lessons of Massachusetts" is that the key lock-in point for Microsoft's monopoly is their iron fisted control of the productivity environment, anchored by MSOffice and the Windows local workgroup client/server system.  Key to office productivity is the compound document model that fuels every business process and business productivity system.  It's the embedded logic and database connectivity (OLE, ODBC, MAPI and COM ActiveX controls) that juice the compound document model.   Convert a compound document to another format (or PDF), and you BREAK the both the document, AND THE BUSINESS PROCESS!!!! It was the breaking of the business process that stopped Massachusetts from moving to the Open Document Format !!!! So now comes a story with consumer sales vs enterprise sales numbers that seemingly shatter the Lessons of Massachusetts.  How is that? My take is that the numbers Microsoft touts are true.  Consumers are making new purchases - NOT enterprises.  The simple truth is that, as Microsoft introduces new OS and Application Services geared to Mobile / Cloud Computing, these new systems BREAK legacy business systems.  It's still way too costly for businesses to transition to the new models. Eventually though, businesses will replace those legacy business productivity systems with Mobile / Cloud Computing systems.  And it will be a rip-out-and-replace transition; not the gradual "value-added" transition everyone hopes Microsoft will provide.   Interesting stuff. excerpt: "If Microsoft is an enterprise company, then why is it spending so much time and money on stuff like Bing, Xbox, Windows Phone, and the Surface RT? It should be going all-in on cloud computing and services. If you were to ask Microsoft's CEO Steve Ballmer, his answer would probably be: It's a dumb question, we're both. In an interview with Jason Pontin at MIT Technology Review, he said: ""Our number-one thing is supplying products to consumers. That's kind of what we do.

Note that rip-out-and-replace to get to the cloud is a very risky strategy for MSFT because the company forfeits its vendor lock-in advantage; the question for the enterprise then becomes "replace with what?" The answer in many cases will be non-Microsoft services. And traditionally, what the enterprise uses has driven what enterprise workers use at home far more than vice versa.

"You have to think that the addition of apps to Office 365 is the continuation of the evolution of documents from static entities that only change when you change them, to living creations that that can update themselves. And by giving documents apps, Microsoft essentially is transforming documents into apps … all the while and not incidentally giving you, me, and any Joe Blow Nonprogrammer the ability to build things that only short years ago would have required extensive development. Not only is Microsoft is making office productivity tools more like the web, it's giving us the ability to create mashups of data and analysis and visualization on the fly. "

Is Intel right?  Is there a "compatibility-interoperability" problem between Windows RT Office (ARM) and legacy (x86) Windows MS Office productivity environments?  It seems to me that the entire reason iPAD, Android and other ARM based tablet systems want MSOffice and MSOffice Visual Document Viewers is exactly because they want and expect a high level of compat-interop with legacy Windows productivity workgroups and client/server systems. What's the truth?  And is there anything x86 providers like Intel and AMD can do about compat-interop and the unstoppable cloud-mobility revolution? excerpt: The Asus tablet has a quad-core Tegra 3 processor from Nvidia. Windows RT comes preloaded with Office 15, a group of widely used productivity applications. Microsoft has said it had to re-engineer Windows RT to deal with expectations for ARM based devices, which include all-day connectivity and low power consumption. The tablet also has an 8-megapixel camera at the rear with LED flash, and a 2-megapixel camera at the front. It has 2GB of RAM, 32GB of storage, Wi-Fi and Bluetooth 4.0. Intel has already started the war of words against ARM around Windows 8, with Intel's CEO Paul Otellini saying that ARM devices will be incompatible with existing Windows applications and drivers. But analysts have said that Windows RT devices will likely be attractive to users who have few ties with legacy Windows PCs. Low prices could also attract users to Windows on ARM devices.