Skip to main content

Home/ Open Web/ Group items tagged web-office

Rss Feed Group items tagged

Gary Edwards

Overview of apps for Office 2013 - 0 views

  •  
    MSOffice is now "Web ready".  The Office apps are capable of running HTML5-JavaScript apps based on a simple Web page model.  Think of this as the Office apps being fitted with a browser, and developers writing extensions to run in that browser using HTML5 and JavaScript.  Microsoft provides an Office.js library and, a developer "Web App/Page Creator"  Visual Basic toolset called "Napa" Office 365 Development Tools.  Lots of project templates. Key MSOffice apps are Word, Excel, PowerPoint and Outlook.  Develop for Office or SharePoint.  Apps can be hosted on any Web Server. excerpt: Microsoft Office 2013 Developer Environment with HTML5, XML and JavaScript.  Office.js library. "his documentation is preliminary and is subject to change. Published: July 16, 2012 Learn how to use apps for Office to extend your Office 2013 Preview applications. This new Office solution type, apps for Office, built on web technologies like HTML, CSS, JavaScript, REST, OData, and OAuth. It provides new experiences within Office applications by surfacing web technologies and cloud services right within Office documents, email messages, meeting requests, and appointments. Applies to:  Excel Web App Preview | Exchange 2013 Preview | Outlook 2013 Preview | Outlook Web App Preview | Project Professional 2013 Preview | Word 2013 Preview | Excel 2013 Preview  In this article What is an app for Office? Anatomy of an app for Office Types of apps for Office What can an app for Office do? Understanding the runtime Development basics Create your first app for Office Publishing basics Scenarios Components of an app for Office solution Software requirements"
Gary Edwards

Office 365 vs. Google Apps: The InfoWorld review | Cloud Computing - InfoWorld - 0 views

  •  
    Clash of the Productivity Clouds: Before we attempt to answer those questions, one thing must be stated flatly: Office 365 and Google Apps are vastly different products. Office 365 is meant to be used with a locally installed version of Office (preferably Office 2010), whereas Google Apps lives 100 percent in the browser. To use a hackneyed metaphor, we're talking apples and oranges. With so many feature variables between the two products, blanket pronouncements don't make a lot of sense. Nonetheless, with the production release of Office 365, the cloud era of desktop productivity software officially kicks into high gear. Office 365 works with Microsoft's Web App versions of desktop Office applications -- Word, Excel, PowerPoint, and OneNote -- so theoretically, you can use it without a locally installed version of Office at all. But most people won't. The real Office 365 ploy is this: Sick of maintaining Exchange and SharePoint servers? No problem. Pay Microsoft and it will run those servers for you -- and throw in the fancy new Lync communications server. Office 365 represents the first time Microsoft has bundled desktop software (Office 2010) with an online service into a single subscription-based offering. But if you have another source of licenses for Office (2010, 2007, or otherwise), or if you want to run just the Office Web Apps (not likely), you can get an Office 365 license without paying for Office.
Gary Edwards

Businesses deploying Office 2010 five times faster than previous version | WinRumors - 1 views

  •  
    Not sure what to make of this news.  XP continues to rule the desktop, Office 2003-2007 the productivity sweet spot.  I have used and researched Office 2010 and emphatically insist that it is a honey-trap for SharePoint and Live.com cloud-computing.  The MS-Cloud becomes THE default hard drive for Office 2010, with social networking-Facebook like contagion based on shared documents, crap collaboration and in-your-face insistent Live.com/Hotmail eMail.  Everytime i wanted to do something in Office 2010, there were 20 road blocks and hurdles MS put in the path forcing their Facebook-virus on my associates and myself.  Incredibly anti-productive.  Yet it's the only cloud-productivity solution capable of easing the difficult transition from desktop to cloud productivity environments.  Office 2010 does this by integrating into legacy desktop productivity  systems just enough that users will not realize until it's too late that a mine filed of hurdles and gotchas lies ahead. excerpt: Businesses are now deploying Office 2010 five times faster than they deployed Office 2007. Office 2010 is also the fastest-selling version of Office in history. "Nearly 50 million people worldwide use Office Web Apps to view, edit, and share their documents from anywhere with a browser and an Internet connection," added Numoto. Microsoft previously revealed in October that the company had sold six million copies of Office 2010. The company didn't reveal any additional sales figures on Wednesday but reaffirmed that the software is selling well. Office is currently used by more than 750 million users worldwide according to Microsoft.
  •  
    I wonder about those numbers. 6 million copies of Office 2010 sold; total of 750 million users of all versions. That makes 0.8 per cent of Office users who had upgraded between June and October of 2010? Five times faster than Office 2007 would make Office 2007 sales in the same period of its release cycle 0.16 per cent of the 750 million, assuming the number of users had remained constant. I suspect there are some apples and oranges in that wood pile, to mix a metaphor. E.g., retail sales that exclude sales to OEMs?
Gary Edwards

Why You Should Upload Documents to Office Web Apps via SkyDrive - 0 views

  •  
    Here it comes - the "rich" Web experience based on integrated but proprietary 2010 technologies from Microsoft.  Note the comparative "advantages" listed in this article describing Microsoft SkyDrive, and comparing to Google Docs. excerpt:  Do you use Microsoft Office programs for creating documents and then use Google Docs to edit these documents online or as an offsite backup? Well, now that Office 2010 and Office Web Apps are available under public beta for free, here are some reasons why you should consider uploading documents, presentations and spreadsheets into Office Web Apps via Windows Live SkyDrive in addition to your Google Docs account. 1. Windows Live SkyDrive supports larger files 2. Document formatting is preserved 3. Native OpenXML file formats 4. Public Documents are in the Lifestream 5. Content is not 'lost in translation'  ....... When you upload a document in Office Web Apps, the application will automatically preserve all the data in that document even if a particular feature is not currently supported by the online applications. For instance, if your PowerPoint presentation contains a slide transition (e.g., Vortex) that is not supported in the online version of Office, the feature will be preserved in your presentation even if you upload it on to Office Web Apps via Windows Live SkyDrive. Later, when you download and open that presentation inside PowerPoint, it would be just like the original version. The content is not 'lost in translation' with Office Web Apps. Are you using Google Docs as a Document Backup Service?  Office Web Apps won't just preserve all the original features of your documents but you can also download entire directories of Office documents as a ZIP file with a simple click.
Gary Edwards

Microsoft Office to get a dose of OpenDocument - CNET News - 0 views

  •  
    While trying to help a friend understand the issues involved with exchanging MSOffice documnets between the many different versions of MSOffice, I stumbled on this oldy but goody ......... "A group of software developers have created a program to make Microsoft Office work with files in the OpenDocument format, a move that would bridge currently incompatible desktop applications. Gary Edwards, an engineer involved in the open-source OpenOffice.org project and founder of the OpenDocument Foundation, on Thursday discussed the software plug-in on the Web site Groklaw. The new program, which has been under development for about year and finished initial testing last week, is designed to let Microsoft Office manipulate OpenDocument format (ODF) files, Edwards said. "The ODF Plugin installs on the file menu as a natural and transparent part of the 'open,' 'save,' and 'save as' sequences. As far as end users and other application add-ons are concerned, ODF Plugin renders ODF documents as if (they) were native to MS Office," according to Edwards. If the software, which is not yet available, works as described, it will be a significant twist to an ongoing contest between Microsoft and the backers of OpenDocument, a document format gaining more interest lately, particularly among governments. Microsoft will not natively support OpenDocument in Office 2007, which will come out later this year. Company executives have said that there is not sufficient demand and OpenDocument is less functional that its own Office formats. Having a third-party product to save OpenDocument files from Office could give OpenDocument-based products a bump in the marketplace, said Stephen O'Grady, a RedMonk analyst. OpenDocument is the native format for the OpenOffice open-source desktop productivity suite and is supported in others, including KOffice, Sun Microsystems' StarOffice and IBM's Workplace. "To the extent that you get people authoring documents in a format that is natively compatible with
Gary Edwards

Is Oracle Quietly Killing OpenOffice? | Revelations From An Unwashed Brain - 1 views

  •  
    Bingo!  Took five years, but finally someone gets it: excerpt:  Great question. After 10 years, OpenOffice hasn't had much traction in the enterprise - supported by under 10% of firms, and today it's facing more competition from online apps from Google and Zoho. I'm not counting OpenOffice completely out yet, however, since IBM has been making good progress on features with Symphony and Oracle is positioning OpenOffice for the web, desktop and mobile - a first. But barriers to OpenOffice and Web-based tools persist, and not just on a feature/function basis. Common barriers include: Third-party integration requirements. Some applications only work with Office. For example, one financial services firm I spoke with was forced to retain Office because its employees needed to work with Fiserv, a proprietary data center that is very Microsoft centric. "What was working pretty well was karate chopped." Another firm rolled out OpenOffice.org to 7,00 users and had to revert back 5,00 of them when they discovered one of the main apps they work with only supported Microsoft. User acceptance. Many firms say that they can overcome pretty much all of the technical issues but face challenges around user acceptance. One firm I spoke with went so far as to "customize" their OpenOffice solution with a Microsoft logo and told employees it was a version of Office. The implementation went smoothly. Others have said that they have met resistance from business users who didn't want Office taken off their desktop. Other strategies include providing OpenOffice to only new employees and to transition through attrition. But this can cause compatibility issues. Lack of seamless interoperability with Office. Just like third-party apps may only work with Office, many collaborative activities force use of particular versions of Office. Today's Web-based and OpenOffice solutions do not provide seamless round tripping between Office and their applications. Corel, with its
Paul Merrell

Last Call Working Draft -- W3C Authoring Tool Accessibility Guidelines (ATAG) 2.0 - 0 views

  • This is a Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) version 2.0. This document includes recommendations for assisting authoring tool developers to make the authoring tools that they develop more accessible to people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, motor difficulties, speech difficulties, and others. Accessibility, from an authoring tool perspective, includes addressing the needs of two (potentially overlapping) user groups with disabilities: authors of web content, whose needs are met by ensuring that the authoring tool user interface itself is accessible (addressed by Part A of the guidelines), and end users of web content, whose needs are met by ensuring that all authors are enabled, supported, and guided towards producing accessible web content (addressed by Part B of the guidelines).
  • Examples of authoring tools: ATAG 2.0 applies to a wide variety of web content generating applications, including, but not limited to: web page authoring tools (e.g., WYSIWYG HTML editors) software for directly editing source code (see note below) software for converting to web content technologies (e.g., "Save as HTML" features in office suites) integrated development environments (e.g., for web application development) software that generates web content on the basis of templates, scripts, command-line input or "wizard"-type processes software for rapidly updating portions of web pages (e.g., blogging, wikis, online forums) software for generating/managing entire web sites (e.g., content management systems, courseware tools, content aggregators) email clients that send messages in web content technologies multimedia authoring tools debugging tools for web content software for creating mobile web applications
  • Web-based and non-web-based: ATAG 2.0 applies equally to authoring tools of web content that are web-based, non-web-based or a combination (e.g., a non-web-based markup editor with a web-based help system, a web-based content management system with a non-web-based file uploader client). Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session (e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Implementing ATAG 2.0 - Appendix E: Real-time content production. Text Editors: ATAG 2.0 is not intended to apply to simple text editors that can be used to edit source content, but that include no support for the production of any particular web content technology. In contrast, ATAG 2.0 can apply to more sophisticated source content editors that support the production of specific web content technologies (e.g., with syntax checking, markup prediction, etc.).
  •  
    Link is the latest version link so page should update when this specification graduates to a W3C recommendation.
Gary Edwards

Office suites in the cloud: Microsoft Office Web Apps versus Google Docs and Zoho | App... - 0 views

  •  
    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.
Gary Edwards

How would you fix the Linux desktop? | ITworld - 0 views

  • VB integrates with COM
  • QL Server has a DCE/RPC interface. 
  • MS-Office?  all the components (Excel, Word etc.) have a COM and an OLE interface.
  •  
    Comment posted 1 week ago in reply to Zzgomes .....  by Ed Carp.  Finally someone who gets it! OBTW, i replaced Windows 7 with Linux Mint over a year ago and hope to never return.  The thing is though, i am not a member of a Windows productivity workgroup, nor do i need to connect to any Windows databases or servers.  Essentially i am not using any Windows business process or systems.  It's all Internet!!! 100% Web and Cloud Services systems.  And that's why i can dump Windows without a blink! While working for Sursen Corp, it was a very different story.  I had to have Windows XP and Windows 7, plus MSOffice 2003-2007, plus Internet Explorer with access to SharePoint, Skydrive/Live.com.  It's all about the business processes and systems you're part of, or must join.   And that's exactly why the Linux Desktop has failed.  Give Cloud Computing the time needed to re-engineer and re-invent those many Windows business processes, and the Linux Desktop might suceed.  The trick will be in advancing both the Linux Desktop and Application developer layers to target the same Cloud Computing services mobility targets.  ..... Windows will take of itself.   The real fight is in the great transition of business systems and processes moving from the Windows desktp/workgroup productivity model to the Cloud.  Linux Communities must fight to win the great transition. And yes, in the end this all about a massive platform shift.  The fourth wave of computing began with the Internet, and will finally close out the desktop client/server computing model as the Web evolves into the Cloud. excerpt: Most posters here have it completely wrong...the *real* reason Linux doesn't have a decent penetration into the desktop market is quite obvious if you look at the most successful desktop in history - Windows.  All this nonsense about binary driver compatibility, distro fragmentation, CORBA, and all the other red herrings that people are talking about are completely irrelevant
Gary Edwards

OpenGoo: Office Productivity in the Cloud « Ahlera | Words from Ahlera - 0 views

  •  
    Another great review for Conrado. Summary: OpenGoo is an open source web/Cloud office where all resources and aspects of contact and project management are linked. This includes eMail, calendar, task, schedules, time lines, notes, documents, workgroups and data. Great stuff. OpenGoo and hosted sister Feng Office are the first Web Office systems to challenge the entire Microsoft Office productivity environment. Very polished, great performance. Excellent use of URI's to replace Win32-OLE functionality. Lacks direct collaboration of Zoho and gDOCS. Could easily make up for that and more with the incorporation of Wave computing (Google). I'm wondering when Conrado will take on the vertical market categories; like Real Estate - Finance? I also think OpenGoo and Feng Office have reached the point where governments would be interested. Instead of replacing existing MSOffice desktops, migrate the project/contact management stuff to OpenGoo, and shut down the upgrade treadmill. Get into the Cloud. I suspect also that Conrado is looking carefully at Wave Computing, and the chellenge of incorporating Wave into OpenGoo.
Gary Edwards

Microsoft Office 2010 Boosts Core Features, Branches Out onto the Web - eWeek - 1 views

  •  
    Extensive review of Office 2010 by Jason Brooks.  Lengthy comment by ge   Is the Web the new productivity platform?      By: Gary Edwards at: 05-27-10 @ 8:02 pm EST     Thanks Jason for the very detailed and thorough review of Office 2010. I was however left with the impression that Office 2010 includes a number of improved (but for the most part existing) desktop features, but the primary value statement involves the new and very advanced features designed for Web based collaboration and productivity. Would it be worthwhile for business users to upgrade from Office 2007 to Office 2010 if not for the new Web collaboration features? And if that's the case, what does that say about the aging desktop productivity platform empire that has served Microsoft so well?
Gary Edwards

Adeptol Viewing Technology Features - 0 views

  •  
    Quick LinksGet a TrialEnterprise On DemandEnterprise On PremiseFAQHelpContact UsWhy Adeptol?Document SupportSupport for more than 300 document types out of boxNot a Virtual PrinterMultitenant platform for high end document viewingNo SoftwaresNo need to install any additional softwares on serverNo ActiveX/PluginsNo plugins or active x or applets need to be downloaded on client side.Fully customizableAdvanced API offers full customization and UI changes.Any OS/Any Prog LanguageInstall Adeptol Server on any OS and integrate with any programming language.AwardsAdeptol products receive industry awards and accolades year after year  View a DemoAttend a WebcastContact AdeptolView a Success StoryNo ActiveX, No Plug-in, No Software's to download. Any OS, Any Browser, Any Programming Language. That is the Power of Adeptol. Adeptol can help you retain your customers and streamline your content integration efforts. Leverage Web 2.0 technologies to get a completely scalable content viewer that easily handles any type of content in virtually unlimited volume, with additional capabilities to support high-volume transaction and archive environments. Our enterprise-class infrastructure was built to meet the needs of the world's most demanding global enterprises. Based on AJAX technology you can easily integrate the viewer into your application with complete ease. Support for all Server PlatformsCan be installed on Windows   (32bit/64bit) Server and Linux   (32bit/64bit) Server. Click here to see technical specifications.Integrate with any programming languageWhether you work in .net, c#, php, cold fusion or JSP. Adeptol Viewer can be integrated easily in any programming language using the easy API set. It also comes with sample code for all languages to get you started.Compatibility with more than 99% of the browsersTested & verified for compatibility with 99% of the various browsers on different platforms. Click here to see browser compatibility report.More than 300 Document T
Gary Edwards

ODF Plugfest: Making office tools interoperable [LWN.net] - 0 views

  • ODF on the web 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 <office:styles> and <office:automatic-styles> 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.
  •  
    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
Gary Edwards

Office to finally fully support ODF, Open XML, and PDF formats | ZDNet - 0 views

  •  
    The king of clicks returns!  No doubt there was a time when the mere mention of ODF and the now legendary XML "document" format wars with Microsoft could drive click counts into the statisphere.  Sorry to say though, those times are long gone. It's still a good story though.  Even if the fate of mankind and the future of the Internet no longer hinges on the outcome.  There is that question that continues defy answer; "Did Microsoft win or lose?"  So the mere announcement of supported formats in MSOffice XX is guaranteed to rev the clicks somewhat. Veteran ODF clickmeister SVN does make an interesting observation though: "The ironic thing is that, while this was as hotly debated am issue in the mid-2000s as are mobile patents and cloud implementation is today, this news was barely noticed. That's a mistake. Updegrove points out, "document interoperability and vendor neutrality matter more now than ever before as paper archives disappear and literally all of human knowledge is entrusted to electronic storage." He concluded, "Only if documents can be easily exchanged and reliably accessed on an ongoing basis will competition in the present be preserved, and the availability of knowledge down through the ages be assured. Without robust, universally adopted document formats, both of those goals will be impossible to attain." Updegrove's right of course. Don't believe me? Go into your office's archives and try to bring up documents your wrote in the 90s in WordPerfect or papers your staff created in the 80s with WordStar. If you don't want to lose your institutional memory, open document standards support is more important than ever. "....................................... Sorry but Updegrove is wrong.  Woefully wrong. The Web is the future.  Sure interoperability matters, but only as far as the Web and the future of Cloud Computing is concerned.  Sadly neither ODF or Open XML are Web ready.  The language of the Web is famously HTML, now HTML5+
Gary Edwards

Microsoft's Answer to the Web Platform Threat? CHEAT!!!! - Microsoft Web Apps are actu... - 0 views

  •  
    For most of this decade, web developers have been suffering the shortcomings of Internet Explorer. Like 1998 limited HTML-CSS support.  And nothing for the language of the Web - HTML+ :: HTML5, CSS3, SVG/Canvas and advanced JavaScript.  That hasn't bothered Microsoft (NSDQ: MSFT) too much, because the company has historically focused on developing "real" applications that run only on Windows and don't use the browser as a platform. With the new Office web apps, many thought that Microsoft might actually have to experience the living nightmare that web app development can be. Yet the company has figured out a way to make things easier: cheat.   MIcrosof thas figured out how to provide MSOffice as Web Apps, without having to use the language of the Web: HTML+.  Instead, they use protpietary formats, protocols and interfaces to create an interesting dichotomy - a rich MS-Web, and a poor, 1998 Open-Web.
Gary Edwards

Microsoft Links Office With Win 7 - IBD - Investors.com - 0 views

  •  
    In this interview with Microsoft's Chris Capossela, he admits that OOXML is not an interoperable format - that using OOXML will result in a loss of productivity.   excerpt: "The collaboration experience end users are going to have with Office 2010 and the Web applications in the browser and Office on the phone is far superior to anything out there, whether it's from Google or anybody else. And the increase in costs to do what they're suggesting and the decrease in productivity that's going to result is something that customers will see, and then they'll choose Microsoft. The best example of that is just sharing a document. Just taking an Office document that was built in the rich client that has a piece of smart art and a watermark or a header or a footer, and then when I share that with you and you open it in the Office Web app, it looks absolutely identical to what I created. When you make edits to it and save it and I open it back up, I see exactly the edits you made and all the stuff I had in there originally. If you do that exact same thing with Google or Zoho or OpenOffice, you lose stuff. And that means loss of productivity."
Gary Edwards

How Google's Ecosystem Changes Everything | BNET Technology Blog | BNET - 0 views

  •  
    Michael Hickins separates the platform forest from the application trees, putting the focus of the future where it belongs - the movement of the legacy MSOffice Productivity Environment to the Web.  The only question will be which Web?  The Open Web?  Or the MS-Web? excerpt:  Microsoft and Apple have leveraged a particular dominant proprietary platform (Windows/Office in one case, the iPhone/iTunes duopoly in the other) to turn every other vendor into a bit player; and by allowing other vendors to sell products or services that integrate with theirs, they offer just enough incentives for the others to play along. Google is also leveraging a dominant platform (in this case, the Web, the largest platform there is) just as relentlessly as Microsoft and Apple have done, but with an open source philosophy that encourages others to compete. The ecosystem includes everything from a development platform to application suites, but its strength emanates from a basic understanding of what it takes to dominate technology: you have to control what former Open Document Foundation director Gary Edwards calls the "point of assembly" - that crucial spot where end users have to come in order to save, share and retrieve their documents - the final work product that all this technology is meant to help create. What Google is in the process of doing is moving that point of assembly from the desktop, where Microsoft and Apple rule, to the Web, where Google is king.
Gary Edwards

Why Microsoft's Office 365 will clobber Google Apps | VentureBeat - Peter Yared - 0 views

  •  
    Good comparison of Microsoft and Google "Cloud" initiatives.  Sure, Microsoft has the numbers.  They own the legacy desktop productivity platform.  But their execution in the Cloud is horrific.  Businesses will always opt for integrating existing desktop apps with Cloud productivity systems over rip-out-and-replace platform alternatives.   But the benefits of highly interoperable and universally accessible Cloud communications and collaborative computing have to be there.  So far MS has failed to deliver, and miserably so.   excerpt:  With Office 365, Microsoft has finally delivered an end-to-end cloud platform for businesses that encompass not only its desktop Office software, but also its server software, such as Exchange and SharePoint. Contrary to Google's narrative, cloud based office software is still a wide open market. The three million businesses that have "Gone Google" - proclaimed on billboards in San Francisco airport's new Terminal 2 - are for the most part Gmail users, who are still happily using Microsoft Office and even Microsoft Outlook. Gmail is a fast, cheap, spam-free and great solution for business email, especially relative to the expensive, lumbering email service providers. Google Apps has definitely found a niche for online collaboration, but generally for low-end project management types of spreadsheets and small documents. The presentation and drawing Google Apps are barely used. Yes, there are definitely Google Apps wins, since it seems cheap. On implementation, businesses find that switching to Gmail is one thing, but switching their entire business infrastructure to Google Apps is a completely different animal that goes far beyond simply changing how employees are writing memos.
Gary Edwards

Microsoft Office fends off open source OpenOffice and LibreOffice but cloud tools gain ... - 0 views

  •  
    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.
Gary Edwards

Google acquisitions may signal big push against Microsoft Office | VentureBeat - 0 views

  •  
    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.
1 - 20 of 86 Next › Last »
Showing 20 items per page