Group items matching

in title, tags, annotations or url

excerpt: The trend in Office development is the migration of solutions away from in-application scripted processing toward more data-centric development. Of course this is a primary purpose of Open XML, and it is great to see the amount of activity in this area. We've seen customers scripting Word in a server environment to batch process / print documents or for other automation tasks. In reality Word isn't built to do that on a large scale, it is better to work directly against the document rather than via the application whenever possible. The Open XML SDK unlocks a "whole nuther" environment for document processing, and gets you out of the business of scripting client apps on servers to do the work of a true server application (not to mention the licensing problems created by installing Office on a server). comment:  Gray makes a very important point here.  The dominance of the desktop based MSOffice Productivity Environment was largely based the embedded logic driving "in-process" documents that was application and platform (Win32 API) specific.  Tear open any of these workgroup-workflow oriented compound documents and you find application specific scripts, macros, OLE, data bindings, security settings and other application specific settings.  These internal components are certain to break whenever these highly interactive and "live" compound documents are converted to another format, or application use.  This is how MSOffice documents and the business processes they represent become "bound" to the MSOffice Productivity Environment. What Gray is pointing to here is that Microsoft is moving the legacy Productivity Environment to an MSWeb based center where OpenXML, Silverlight, CAML, XAML and a number of other .NET-WPF technologies become the workgroup drivers.  The key applications for the MS WebStack are Exchange/SharePoint/SQL Server.  To make this move, documents had to be separated from the legacy desktop Productivity Environment settings. Note th

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

Amazon releases a new version of the KF8 Format, with greatly improved HTML5-CSS3 capabilities.  Details of the KF8 spec can be found here: http://goo.gl/XY39v A couple of things i'm wondering about here.  One is, the KindleGen conversion tool can convert HTML, XHTML and EPUB to KF8.  Has anyone tried to push a OpenOffice XHTML compound document through this latest KF8 version of  KGen?  I'm thinking that perhaps the OOo HTML problem could be solved in this way? There is no doubt in my mind that HTML5 will continue to grow, and eventually replace the desktop XML "compound document" formats. The great transition from desktop client/server business productivity environments, where legacy compound documents rule the roost and fuel the engines of all business systems, to a Cloud Productivity Platform, will require an HTML5 compound document format model.  Also needed will be HTML5 capable applications participating in the production of Cloud ready compound documents.  Is KF8 a reasonable starting place? excerpt: Kindle Format 8 is Amazon's next generation file format offering a wide range of new features and enhancements - including HTML5 and CSS3 support that publishers can use to create all types of books. KF8 adds over 150 new formatting capabilities, including drop caps, numbered lists, fixed layouts, nested tables, callouts, sidebars and Scalable Vector Graphics - opening up more opportunities to create Kindle books that readers will love. Kindle Fire is the first Kindle device to support KF8 - in the coming months KF8 will be rolled out to our latest generation Kindle e-ink devices as well as our free Kindle reading apps.

Comments on the latest SVN article mulling the effects of Judge Thomas Penfield Jackson's anti trust ruling and proposed break up of Microsoft. comment: "Chinese Wall" Ummm, there was a Chinese Wall between Microsoft Os and the MS Applciations layer. At least that's what Chairman Bill promised developers at a 1990 OS/2-Windows Conference I attended. It was a developers luncheon, hosted by Microsoft, with Chairman Bill speaking to about 40 developers with applications designed to run on the then soon to be released Windows 3.0. In his remarks, the Chairman described his vision of commoditizing the personal computer market through an open hardware-reference platform on the one side of the Windows OS, and provisioning an open application developers layer on the other using open and totally transparent API's. Of course the question came up concerning the obvious advantage Microsoft applications would have. Chairman Bill answered the question by describing the Chinese Wall that existed between Microsoft's OS and Apps develop departments. He promised that OS API's would be developed privately and separate from the Apps department, and publicly disclosed to ALL developers at the same time. Oh yeah. There was lots of anti IBM - evil empire stuff too :) Of course we now know this was a line of crap. Microsoft Apps was discovered to have been using undocumented and secret Window API's. http://goo.gl/0UGe8. Microsoft Apps had a distinct advantage over the competition, and eventually the entire Windows Productivity Platform became dependent on the MSOffice core. The company I worked for back then, Pyramid Data, had the first Contact Management application for Windows; PowerLeads. Every Friday night we would release bug fixes and improvements using Wildcat BBS. By Monday morning we would be slammed with calls from users complaining that they had downloaded the Friday night patch, and now some other application would not load or function properly. Eventually we tracked th

wow.  Six years and all they have migrated are 2,500 out of 14,0000 desktops!  The curse of the Microsoft Productivity Environment strikes again as legacy workgroups, workflows and the mesh of compound documents that drive them prove to be very stubborn.  The funny thing is that, as Munich struggles with this 1995 level desktop transition, Microsoft is preparing to move those very same legacy productivity environments to a proprietary Web Productivity Platform.  I wonder what Munich's Web plans are? excerpt: Schießl says the transition required enormous background effort which involved eliminating many IT dependencies created by individual vendors over the years. More than 20,000 templates had to be consolidated and converted into new templates, macros or web applications. Most templates and text blocks are now managed via the WollMux program, which was released in 2008. Schießl said that the developers also had to adapt a number of corporate applications such as SAP for use with ODF. According to the review, another achievement in 2009 was the establishment of Linux client pilot areas as a step towards the final aim of migrating all twelve of the city administration's departments to Linux. Schießl says this was the last fundamental step required to enable general client migration in the coming years. Although only 2,500 of around 14,000 workstations have been converted to the custom-built basic LiMux client, the hardest part was to get them all up and running, which required going over inconsistent IT infrastructures that had developed over the years and training the IT staff for the technical switch. As Robert Pogson observes in his blog, six and a half years after the decision was made to switch to free software, the Munich Linux pioneers have completed about 80 per cent of the project's total workload.

Good discussion and review of office suites, desktop publishing tools, wordprocessors, time management, and drawing/illustration tools.  covers: AbiWord, Scribus, SeaMonkey, GIMP, Paint.net, InkScape, Dia, GTD-Free (Getting Things Done), and Task Coach.  +1 for InkScape Tagged PDF editing and Paint.net as a Adobe Illustrator replacement.

Byron Deeter is right, but perhaps he's holding back on his reasoning.  Silicon Valley is all about platform, and platform plays only come about once every ten to twenty years.  They come like great waves of change, not replacing the previous waves as much as taking away and running with the future.   Cloud Computing is the fourth great wave.  It will replace the PC and Network Computing waves as the future.  It is the target of all developers and entrepreneurs.   The four great waves are mainframe, workstation, pc and networked pc, and the Internet.  Cloud Computing takes the Internet to such a high level of functionality that it will now replace the pc-netwroking wave.  It's going to be enormous.  Especially as enterprises move their business productivity and data / content apps from the desktop/workgroup to the Cloud.  Enormous. The key was the perfect storm of 2008, where mobility (iPhone) converged with the standardization of tagged PDF, which converged with the Cloud Computing application and data model, which all happened at the time of the great financial collapse.   The financial collapase of 2008 caused a tectonic shift in productivity.  Survival meant doing more with less.  Particularly less labor since cost of labor was and continues to be a great uncertainty.  But that's also the definition of productivity and automation.  To survive, companies were compelled to reduce labor and invest in software/hardware systems based productivity.  The great leap to a new platform had it's fuel; survival. Social applications and services are just the simplest manifestation of productivity through managed connectivity in the Cloud.  Wait until this new breed of productivity reaches business apps!  The platform wars have begun, and it's for all the marbles. One last thought.  The Internet was always going to win as the next computing platform wave.  It's the first time communications have been combined and integrated into content, and vast dat

Good title.  Nice to see that some of the tech media are starting to figure this out.  It's about time. excerpt: While Microsoft has struggled with its mobile operating system, it still occupies a dominant stake of the server operating system, desktop operating system, business productivity software, messaging, and Web browser markets. Bells and whistles aside, it's hard to argue with the potential of a smartphone platform that can seamlessly tie in with the platforms and tools that businesses rely on. RIM, Apple, Palm, and now Google, all recognize and respect Microsoft's presence in the enterprise. These other mobile platforms realize that integration with Microsoft backend tools--particularly Exchange Server--is imperative to success in the enterprise. No matter how hard they try, though, the solutions are often clumsy or cumbersome, and have a sort of "square peg in the round hole" feel to them. The core appeal of a Microsoft mobile operating system is the inclusion of native tools that naturally integrate with the existing server, desktop, and office productivity environment. Windows Mobile is uniquely suited to deliver a seamless and familiar experience for business professionals. Expecting Microsoft to introduce unique innovations or raise the bar in any way for mobile operating systems is probably a recipe for disappointment. Assuming that Microsoft can at least improve Windows Mobile to the point that Windows Phones are more or less on par with next-generation smartphones like the iPhone or Droid will be enough, though, for Microsoft to get the ship pointed in the right direction and begin to reclaim some of its lost mobile platform market share. Microsoft has a built-in audience and the game is Microsoft's to lose.

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.

Lengthy discussion about Cloud computing innovation and interoperability.  Lots of quotes.  Looks like the consulting space for cloud computing is exploding.  No mention though of the great transition from Desktop/WorkGroup Productivity to Cloud/Web Productivity Platforms.  Obviously we need more experts :) excerpt: As the hype over cloud computing evolves into a more substantive discussion, one thing has become clear -- customers do not want to be locked into a single cloud provider. They would like the freedom to move among the clouds -- ideally from public to private and back again. This would give customers the freedom to switch providers as their computing needs grow or shrink, and the ability to move applications and workloads around as their business requirements change.

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.

.... "While i don't see Google or anyone else replacing the MSOffice productivity environment anytime soon, i do see Google challenging Microsoft wherever the Web comes into play. As for the future, that battle for desktop productivity will take place, just not with ChromeOS, Linux, or, the MacOS. What has to happen before the assault on the Microsoft's productivity empire can begin is that the business systems bound to the MSOffice productivity environment must transition to the Open Web, via SaaS or some other replacement. Or, the productivity environment itself must be re-purposed to the Open Web. The tricky part will be that re-purposing play. ChromeOS is a blockbuster announcement. Not a declaration of war, but a shot across the bow that shouts; Google will defend the Open Web, and profitable business they have there. ..... ~ge~

Real-time co-creation and co-editing: With Novell Vibe, people in your organization can author and edit online documents together, character by character, in real time. Teams can dramatically accelerate the completion of projects that used to take weeks. Because collaboration unfolds in a shared workspace, no one has to manually merge content from multiple contributors to create a unified, finished document. Enterprise social messaging: As easy to use as Facebook or Twitter, Novell Vibe consolidates direct messages, chat, blogs and wikis from within Novell Vibe into one message stream. Creating new groups and inviting members from inside or outside your organization is as simple as sending an e-mail. You can even jumpstart ad-hoc conversations in seconds to tackle projects that can't wait. File synchronization and management: Files on your desktop, regardless of authoring application, can be synchronized to the Novell Vibe file repository based in the cloud. As a result, users always work with the latest versions of important files on their desktops and in Novell Vibe. The Novell Vibe unified message stream: Direct messages, social feeds and group conversations from within Novell Vibe are unified in one intuitive interface. This eliminates the need to constantly switch between locations to see all your content. Using powerful filtering, sorting and tagging capabilities, you can determine exactly what you want to see and whom you want to follow. Advanced information management: Novell Vibe keeps a persistent record of all your work and conversations. Its comprehensive search function quickly locates files, messages, attachments, groups and people to save time and boost productivity.

Good discussion, but it really deserves a more in-depth thrashing.  The basic concept is that a perfect storm of mobility, cloud-computing and HTML5-JavaScript has set the stage for a major, massive shift in application development.  The shift from C++ to Java is now being replaced by a greater shift from Java and C++ to JavaScript-JSON-HTML5. Interesting, but i continue to insist that the greater "Perfect Storm" triggered in 2008, is causing a platform shift from client/server computing to full on, must have "cloud-computing".   There are three major "waves"; platform shifts in the history of computing at work here.  The first wave was "Mainframe computing", otherwise known as server/terminal.  The second wave was that of "client/server" computing, where the Windows desktop eventually came to totally dominate and control the "client" side of the client/server equation. The third wave began with the Internet, and the dominance of the WWW protocols, interfaces, methods and formats.  The Web provides the foundation for the third great Wave of Cloud-Computing. The Perfect Storm of 2008 lit the fuse of the third Wave of computing.  Key to the 2008 Perfect Storm is the world wide financial collapse that put enormous pressure on businesses to cut cost and improve productivity; to do more with less, or die.  The survival maxim quickly became do more with less people - which is the most effective form of "productivity".  The nature of the collapse itself, and the kind of centralized, all powerful bailout-fascists governments that rose during the financial collapse, guaranteed that labor costs would rise dramatically while also being "uncertain".  Think government controlled healthcare. The other aspects of the 2008 Perfect Storm are mobility, HTML5, cloud-computing platform availability, and, the ISO standardization of "tagged" PDF.   The mobility bomb kicked off in late 2007, with the introduction of the Apple iPhone.  No further explanation needed :) Th

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.

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.  

PALO ALTO, Calif., January 12, 2010 - VMware, Inc. (NYSE: VMW), the global leader in virtualization solutions from the desktop through the datacenter and to the cloud, today announced that it has entered into a definitive agreement to acquire Zimbra, a leading vendor of email and collaboration software, from Yahoo! Inc. Zimbra is a leading open source email and collaboration solution with over 55 million mailboxes.  As an independent Yahoo! product division, Zimbra achieved 2009 mailbox growth of 86% overall and 165% among small and medium business customers.

Dion Hinchcliffe has an excellent article casting Google Wave as an Enterprise game-changer. He walks through Wave first, and then through some important enterprise features: ".....to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community: Google Wave has three layers: the product, the platform, and the protocol: The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave). Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves. The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

excerpt: "Developer-led or services-led? Microsoft should get an early advantage, but the services strategy by Cisco should create longer, more sustainable value, Last month I wrote a blog outlining how the line-of-business manager holds the key to winning the Cisco versus Microsoft war. A number of you commented that this was obvious and both companies are already doing it. I'll agree that this is something both companies are trying to do, but neither is doing a great job. Microsoft is a company with high appeal to IT pros and Cisco to network managers, with high brand familiarity to line of business managers but low appeal beyond this."