Skip to main content

Home/ Open Web/ Group items matching "productivity-environment" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

YouTube flushes Flash for future flicks * The Register - 0 views

www.theregister.co.uk/...lushes_flash_for_future_flicks

HTML5 Flash Youtube

shared by Paul Merrell on 28 Jan 15 - No Cached

  • YouTube has decided it's had enough of Adobe's perenially-p0wned Flash and will therefore now default to delivering video with the HTML5 <video> tag.

    A post by the video vault's engineering and development team says the move is now possible, and sensible, because the industry has invented useful things like adaptive bitrates, encryption, new codecs and WebRTC that make the <video> usable work in the real world.

    Those additions mean HTML5 is at least as functional – or more so – than Flash, and if YouTube detects you are running Chrome, IE 11, Safari 8 and beta versions of Firefox, it'll now deliver video using <video> and flush Flash.

    YouTube's also decided to can what it calls the “'old style' of Flash embeds and our Flash API. We encourage all embedders to use the iframe API, which can intelligently use whichever technology the client supports.”

  • YouTube seems not to care a jot that its actions are inimical to Adobe, saying it's just doing what all the cool kids – Netflix, Apple, Microsoft and its competitor Vimeo – have already done. Which is not to say that Flash is dead: those who don't run the browsers above will still get YouTube delivered by whatever technology works bes tin their environment. And that will often – perhaps too often* – be Flash. ® Bootnote * Until they get p0wned, that is: Flash is so horridly buggy that Apple has just updated its plugin-blockers to foil versions of the product prior to 16.0.0.296 and 13.0.0.264.
Paul Merrell

Mozilla partners with Panasonic to bring Firefox OS to the TV, details progress on tablet and desktop versions - The Next Web - 0 views

thenextweb.com/...s-work-tablet-desktop-versions

Firefox-OS

shared by Paul Merrell on 07 Jan 14 - No Cached
  • At CES 2014 in Las Vegas today, Mozilla announced its plans for Firefox OS this year. Having launched Firefox OS for smartphones in 2013, the company has now partnered with Panasonic to bring its operating system to TVs, and also detailed the progress that has been made around the tablet and desktop versions.
  • Mereby elaborated that current options are controlled by either Google or Apple, two major corporations that “hold all the strings.” As such, Android and iOS are not viable options for Panasonic, as the ecosystem is tightly controlled. With Firefox OS, however, Mereby argues that “anyone can compete”, as you can operate your own marketplace. Not only can Panasonic open up its own marketplace for apps and content, but those who want to build apps and sell content can bypass marketplaces and make their offerings directly to Firefox OS users.
  • While the partnership is not exclusive, Panasonic will be the first to release next-generation smart TVs powered by Firefox OS. Mozilla and Panasonic will work together to promote Firefox OS and its open ecosystem on the big screen. The plan is to leverage existing HTML5 and Web technologies used on PCs, smartphones, and tablets, to provide TVs with more personalized and optimized access to content and services through the Internet. Mozilla’s Web APIs for hardware control and operation will allow TVs to monitor and operate devices, such as emerging smart home appliances, inside and outside of the home. Basic functions such as menus and programming guides, which are currently written as embedded programs, will be written in HTML5, letting developers easily create applications for smartphones or tablets to remotely access and operate TVs. Mozilla also envisions personalized user interfaces with users’ favorites and new functions for multiple users sharing the same screen.
  • ...1 more annotation...
  • Last but not least, Mozilla wanted to underline how Firefox OS was coming to the desktop. Since the operating system is open source, anyone can modify it. VIA is doing just that: it’s making its own changes to create a more suitable version for the desktop, and Mozilla is bringing those commits back to its own repository. Furthermore, VIA today announced the availability of APC Paper and Rock, two new devices that offer a preview of Firefox OS running in a desktop environment. Rock is a motherboard which can be inserted into any barebone PC chassis while Paper is a standalone computer with its own case. Both are targeted at early adopters and developers wanting to help find, file, and fix bugs for VIA’s desktop version of Firefox OS. Paper and Rock are available with the same buildable source codes currently available on GitHub.
Gary Edwards

XML Production Workflows? Start with the Web and XHTML - 1 views

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 01 Nov 13 - No Cached
  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Using the Web as a Production Platform
  • Gary Edwards on 01 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. As an after thought, i was thinking that an alternative title to this article might have been, "Working with Web as the Center of Everything".
Gary Edwards

Is productivity in the workplace possible with Surface 2 or iPad? | ZDNet - 0 views

www.zdnet.com/h-surface-2-or-ipad-7000022220

Cloud-Computing Cloud-Productivity-Platform mobile-computing business-productivity

shared by Gary Edwards on 22 Oct 13 - No Cached
  • Gary Edwards on 22 Oct 13
     
    Not surprisingly, Microsoft is going to pound on "productivity" as the key differential between their desktop-cloud-mobile computing products, and those of mobile-productivity platform challengers, Apple and Google. There are three platform contenders, and this article points out that it is Google Apps that is keeping Apple in the business productivity game. Very interesting insight. Especially since a recent Forrester Report has the Apple platform capturing 65% of all mobile business application development. And Microsoft with only 1%. Google weighs in with 13%. This is a stunning setback for Microsoft. The MS monopolist empire is built on business productivity, with 98% of clinet/server marketshare. excerpt: "Over time, Microsoft has tried to tilt the marketing message to position Surface as a "productivity tablet". Now that Surface 2 is out, the "productivity tablet" message is coming across loud and clear. But can what people use tablets at work for actually be described as "productive"? Surface might be new, but the idea of using tablets in business is not. Although Microsoft would like us to believe that a tablet that doesn't run Office and doesn't have a good solution for a keyboard can't be used in business, the iPad has been used in business since its release in April 2010. Mobile device management (MDM) allows enterprises to control which apps are available on both on BYOD and enterprise-supplied tablets. Some MDM vendors publish reports and surveys on what their customers' allow and disallow. This information can provide some insight into what apps people are typically using. Back in June, my ZDNet colleague Adrian Kingsley-Hughes reported on a report put out by one such vendor. Fiberlink gave this list of iOS apps that are commonly whitelisted: iBooks Adobe Reader Google Citrix Receiver Numbers Dropbox Pages iTunes U Keynote WebEx Along with those apps, you also need to add that apps that come with the device - namely web browsing, email,
Gary Edwards

No Jitter | Post | Cisco Or Microsoft? Who Wins the Line-of-Business War? - 0 views

www.nojitter.com/...ho-wins-the-lineofbusiness-war

Cloud-Productivity-Platform

shared by Gary Edwards on 23 Jul 13 - No Cached
  • The multitude of services gives Microsoft an early edge when it comes to cloud, but the channel-enablement model for Cisco can create much greater scale than a direct to line-of-business model. The key is ensuring its resellers are fully trained in selling to line-of-business, which isn't a simple undertaking. Bottom line: With regard to cloud, Microsoft has a faster route to market, but Cisco's should give it an advantage over time.
  • Putting cloud aside, Cisco and Microsoft have markedly different approaches in selling to lines of business. For Microsoft, the key lies in its developer community. Developers build applications that business people use and buy. Many of these applications use Microsoft as an underlying technology without the purchaser really even being aware of that fact. Microsoft gets pulled through with really no involvement from Microsoft, providing a low- to no-cost sales model for the company. The only down side is that the application brand often overshadows the underlying brand.
  • With regards to UC, as this market transitions away from products to platforms, services will play a significant role. Cisco's services plays a role similar to IBM services. IBM's consulting group works with its top tier customers to understand how to solve business problems through compute-centric solutions. Cisco services works with its customers to create solutions through networking- and communications-related products. As more and more organizations look to leverage UC strategically, I would expect Cisco services to target its top-tier customers. The key for Cisco then is to take these solutions and push them down through its channel for scale and market share gains.
  • ...6 more annotations...
  • Cisco has been trying to build its own "Cisco Developer Network" (CDN) for the better part of a decade. The company kicked off this initiative way back in the early 2000s when it bought a company called Metreos that had some interesting VoIP applications and a slick developer interface. Back then, the program was known as CTDP, Cisco Technology Developer Program, and was run by VoIP people, not individuals that understand software and how to build a developer environment. Since then the program has undergone a number of facelifts and Cisco appears to have some real software people running the group, so there is some potential.
  • Microsoft has made a living off selling products, many of them sub-par, into business because of its developer relationships. Does anyone really think Microsoft gained monopoly-like share with desktop operating systems because of quality of product and ease of use? Hardly. Windows became the de facto standard for developers because of the quality of the developer program. Microsoft does a good job of meeting the needs of its large software vendors, but does an even better job of making sure those millions of small ISVs have access to Microsoft platforms and developer support.
  • So developer-led or services-led?
  • Microsoft should get an early advantage, as many in-house developers will look to Lync; but the services strategy by Cisco should create longer, more sustainable value, as it has for IBM.
  • The key for Microsoft is being able to adapt its developer environment faster as market trends change. Obviously, compute is moving away from the traditional desktop to mobile clients and the cloud, and there are far more single-use, purpose-built applications being built in the consumer world. I think Microsoft's Developer Network is oriented towards more old-school developers.
  • The key for Cisco is having the patience to work with its lead customers and find those unique, game-changing applications and use cases that it can then push down into the channel. It's the right strategy for Cisco, but it might take a bit more time to bear some fruit.
  • Gary Edwards on 23 Jul 13
     
    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."
Gary Edwards

Two Microsofts: Mulling an alternate reality | ZDNet - 0 views

www.zdnet.com/n-alternate-reality-7000016916

Microsoft microsoft-monopoly Judge-Thomas-Penfield-Jackson

shared by Gary Edwards on 19 Jun 13 - No Cached
  • Judge Jackson had it right. And the Court of Appeals? Not so much
  • Judge Jackson is an American hero and news of his passing thumped me hard. His ruling against Microsoft and the subsequent overturn of that ruling resulted, IMHO, in two extraordinary directions that changed the world. Sure the what-if game is interesting, but the reality itself is stunning enough. Of course, Judge Jackson sought to break the monopoly. The US Court of Appeals overturn resulted in the monopoly remaining intact, but the Internet remaining free and open. Judge Jackson's breakup plan had a good shot at achieving both a breakup of the monopoly and, a free and open Internet. I admit though that at the time I did not favor the Judge's plan. And i actually did submit a proposal based on Microsoft having to both support the WiNE project, and, provide a complete port to WiNE to any software provider requesting a port. I wanted to break the monopolist's hold on the Windows Productivity Environment and the hundreds of millions of investment dollars and time that had been spent on application development forever trapped on that platform. For me, it was the productivity platform that had to be broken.
  • I assume the good Judge thought that separating the Windows OS from Microsoft Office / Applications would force the OS to open up the secret API's even as the OS continued to evolve. Maybe. But a full disclosure of the API's coupled with the community service "port to WiNE" requirement might have sped up the process. Incredibly, the "Undocumented Windows Secrets" industry continues to thrive, and the legendary Andrew Schulman's number is still at the top of Silicon Valley legal profession speed dials. http://goo.gl/0UGe8 Oh well. The Court of Appeals stopped the breakup, leaving the Windows Productivity Platform intact. Microsoft continues to own the "client" in "Client/Server" computing. Although Microsoft was temporarily stopped from leveraging their desktop monopoly to an iron fisted control and dominance of the Internet, I think what were watching today with the Cloud is Judge Jackson's worst nightmare. And mine too. A great transition is now underway, as businesses and enterprises begin the move from legacy client/server business systems and processes to a newly emerging Cloud Productivity Platform. In this great transition, Microsoft holds an inside straight. They have all the aces because they own the legacy desktop productivity platform, and can control the transition to the Cloud. No doubt this transition is going to happen. And it will severely disrupt and change Microsoft's profit formula. But if the Redmond reprobate can provide a "value added" transition of legacy business systems and processes, and direct these new systems to the Microsoft Cloud, the profits will be immense.
  • ...1 more annotation...
  • Judge Jackson sought to break the ability of Microsoft to "leverage" their existing monopoly into the Internet and his plan was overturned and replaced by one based on judicial oversight. Microsoft got a slap on the wrist from the Court of Appeals, but were wailed on with lawsuits from the hundreds of parties injured by their rampant criminality. Some put the price of that criminality as high as $14 Billion in settlements. Plus, the shareholders forced Chairman Bill to resign. At the end of the day though, Chairman Bill was right. Keeping the monopoly intact was worth whatever penalty Microsoft was forced to pay. He knew that even the judicial over-site would end one day. Which it did. And now his company is ready to go for it all by leveraging and controlling the great productivity transition. No business wants to be hostage to a cold heart'd monopolist. But there is huge difference between a non-disruptive and cost effective, process-by-process value-added transition to a Cloud Productivity Platform, and, the very disruptive and costly "rip-out-and-replace" transition offered by Google, ZOHO, Box, SalesForce and other Cloud Productivity contenders. Microsoft, and only Microsoft, can offer the value-added transition path. If they get the Cloud even halfway right, they will own business productivity far into the future. Rest in Peace Judge Jackson. Your efforts were heroic and will be remembered as such. ~ge~
  • Gary Edwards on 19 Jun 13
     
    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
Gary Edwards

Google Is Prepping A Sneak Attack On Microsoft Office - ReadWrite - 0 views

readwrite.com/...eak-attack-on-microsoft-office

document-wars Cloud-Productivity-Platform

shared by Gary Edwards on 17 May 13 - No Cached
    • Gary Edwards
      Gary Edwards on 17 May 13
       
      Pretty good quote describing the reach of "Visual Productivity".  Still, the quote lacks the power of embedded data (ODBC) streams and application obects (OLE) so important to the compound document model that sits at the center of all productivity environments and business system automation efforts.
  • In a supporting comment, Zborowski pointed out that Google doesn't support the Open Document Format, suggesting that Microsoft is more open than Google.
    • Gary Edwards
      Gary Edwards on 17 May 13
       
      Now this is funny!!!
  • Productivity software is built to help people communicate. It's more than just the words in a document or presentation; it's about the tone, style and format you use to convey an overall message. People often entrust important information in these documents -- from board presentations to financial analyses to book reports. You should be able to trust that what you intend to communicate is what is being seen.
Gary Edwards

Furious Over End Of Google Reader - Business Insider - 1 views

www.businessinsider.com/er-end-of-google-reader-2013-3

google-reader

shared by Gary Edwards on 16 Mar 13 - No Cached
  • Gary Edwards on 16 Mar 13
     
    "Gary Edwards on Mar 15, 8:25 PM said: There are only three apps i load at boot-up: gMail, gReader, and gWave. Ooops! Google Wave was cancelled over a year ago. Owning the end-users attention at boot-up proved to be an essential factor to the Microsoft monopoly. They built an iron fisted empire out of owning the point of boot-up. So it's very strange to see Google give up the very thing other cloud platform contenders would no doubt kill for. Very strange. Even stranger though is the perception that Google + will somehow now move to center stage? The only reason i use Google+ is because it's easy to point to an article and post a comment from Google Reader to my + circles. Other than that i have no use for +. Nicolas Carr posted an interesting comment on Google's cancellation of gReader yesterday. He tried to argue that there is a difference between "tools" and "platforms", and Google was more interested in building a platform than maintaining "tools" like gReader. So, Google+ is now essential to the Google Platform? Unfortunately, the otherwise brilliant and cosmic insightful Mr. Carr, fails to make that case. Microsoft became a platform when they succeeded in positioning their OS as the essential factor bridging an explosively innovative and rapidly commoditiz'ing Windows hardware reference platform, and, he equally rapid and innovative Windows software application platform. Both software and hardware were being written and developed to the Windows OS, with features doubling and costs being halved at a rate that even Moore's Law envied. Microsoft fully cemented the emerging hardware - OS - application platform with a business productivity environment that necessitated the use of the MS Office suite of servers and apps. That lock on business productivity has yet to be broken. And even though the mighty Google Apps has made some progress convincing businesses to rip-out-and-replace their legacy business productivity systems and re write to the Google Cloud P
Gary Edwards

Steve Ballmer: Consumers Are Our Number One Thing - Business Insider - 3 views

www.businessinsider.com/re-our-number-one-thing-2013-2

Office-Productivity office-in-the-cloud Cloud-Productivity mobile-computing Productivity

shared by Gary Edwards on 27 Feb 13 - No Cached
  • Gary Edwards on 27 Feb 13
     
    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.
  • Paul Merrell on 01 Mar 13
     
    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.
Gary Edwards

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

www.itworld.com/...ow-would-you-fix-linux-desktop

Linux-desktop Brian-Proffitt productivity-environment Cloud-Computing Cloud-Productivity-Platform

shared by Gary Edwards on 20 Sep 12 - No Cached
  • VB integrates with COM
  • QL Server has a DCE/RPC interface.&nbsp;
  • MS-Office?&nbsp; all the components (Excel, Word etc.) have a COM and an OLE interface.
  • Gary Edwards on 20 Sep 12
     
    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

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

www.zdnet.com/xml-and-pdf-formats-7000002696

ODF ODF-interop MSOffice-productivity Cloud-Compound-Document

shared by Gary Edwards on 22 Aug 12 - No Cached
  • Gary Edwards on 22 Aug 12
     
    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

Asus shows off ARM-based Windows 8 tablet - Computerworld - 0 views

www.computerworld.com/...off_ARM_based_Windows_8_tablet

Cloud-Productivity-Platform Visual-Productivity MS-Business-Productivity-Platform Compat-Interop

shared by Gary Edwards on 04 Jun 12 - No Cached
  • Gary Edwards on 04 Jun 12
     
    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.
Gary Edwards

Government Market Drags Microsoft Deeper into the Cloud - 0 views

www.readwriteweb.com/...soft-deeper-into-the-cloud.php

Cloud-Productivity-Platform Microsoft Great-Transition desktop-productivity

shared by Gary Edwards on 02 Jun 12 - No Cached
  • Gary Edwards on 02 Jun 12
     
    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
Gary Edwards

Ray Ozzie's startup has mobility, communications at core - Computerworld - 0 views

www.computerworld.com/...obility_communications_at_core

Ray-Ozzie Cocomo Cloud-Productivity-Platform

shared by Gary Edwards on 13 Mar 12 - No Cached
  • Gary Edwards on 13 Mar 12
     
    Interesting, but lightweight interview with Ray Ozzie.  Look at the productivity comment in particular.  He also mentions "social productivity" as being an aspect of "communications".  My guess is that his new startup, Cocomo, will gear up towards a Cloud Productivity Platform where this new capability of integrated web communications is woven deep into collaborative productivity applications.  With enough juice to blow the legacy Windows - MSOffice Productivity environment out of the water.  We shall see. excerpt: When he joined Microsoft he thought it had a "tremendous history," he said, with great technology assets and people. But it was a company struggling to adjust to changes in the PC and server markets, he said. "I tried my best to communicate with various groups what their purpose in life was," he said. For instance, he tried to convince the Office group that it should focus on selling productivity, as opposed to selling PC-based productivity products, and the Xbox group that it should sell entertainment, not boxes or discs.
Gary Edwards

Kindle Format 8 Overview - 0 views

www.amazon.com/...feature.html

KF8 compound-documents Cloud-Productivity-Platform Cloud-Compound-Document

shared by Gary Edwards on 13 Jan 12 - No Cached
  • Gary Edwards on 13 Jan 12
     
    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.
Gary Edwards

This 32-Year-Old Entrepreneur Is Bent On Beating One Of Microsoft's Largest Businesses - 1 views

www.sfgate.com/...article.cgi

Huddle

shared by Gary Edwards on 08 Dec 11 - No Cached
  • Gary Edwards on 08 Dec 11
     
    Good in depth article about Huddle, and their challenge to Microsoft SharePoint.  We met these guys at the 2006 and 2007 Office 2.0 conference in San Fran.  Lengthy conversations about the Windows Productivity Environment and how Microsoft built that platform.  Need to take a closer look at how far they have come.  The Cloud is a greaqt opportunity for a new Productivity Platform.
Gary Edwards

HTML5 Will Transform Mobile Business Intelligence and CRM - 0 views

www.enterpriseappstoday.com/...business-intelligence-crm.html

HTML5 OpenWeb OpenWeb-Productivity-Platform Cloud-Productivity-Platform Cloud-Compound-Document

shared by Gary Edwards on 18 Oct 11 - No Cached
  • "HTML5 is a big push forward, especially considering how it handles different media as well as cross-device portability," said Tiemo Winterkamp, senior vice president of global marketing at business intelligence (BI) vendor arcplan
  • one big benefit of HTML5 is that browsers will be able to integrate additional content like multimedia, mail and RIA with enhanced rendering capabilities. And plans have been made to allow future HTML5 browsers to securely access sensor and touch information, which makes HTML5 a viable alternative to native application development for such functions.
    • Gary Edwards
      Gary Edwards on 18 Oct 11
       
      The browser becomes the compound document container, but HTML5 is clearly the document format.  Any application or Office Suite capable of creating HTML5 documents, or connecting, linking and embedding information and application services in another apps HTML5 document would be cloud productivity platform ready.  Similar to a local Windows workgroup, the database and transaction processing servers can be in the cloud, connecting to browser based apps and interfaces where the essence of the new compound document is created or interactively expressed.  Kind of cool having GPS built into the information stream instead of having to type in a zip code, and refreshing a legacy compound document or compound chart.
  • With HTML5, nearly every piece of internet content we can envision today will be able to be coded in HTML, Javascript and Cascading Style Sheets (CSS), and therefore automatically portable to all environments and browsers supporting HTML5.
  • ...1 more annotation...
  • "This approach is very attractive for BI vendors who aim to provide business critical information anywhere, anytime and on any device," said Winterkamp. "The result is an attractive, multi-functional user interface with as little design and deployment effort as possible. And more importantly, you only need to develop these apps once for all devices."
  • Gary Edwards on 18 Oct 11
     
    Good article on the increasing use of HTML5 for business apps.  The focus is on mobile devices, even though HTML5 clearly targets anything capable of running a WebKit class browser.  The article also demonstrates, albeit unwittingly, the use of HTML5 as a cloud platform "Compound Document" model.  Something far more important than the comparatively limited focus of BI and CRM mobility apps.   A Cloud Producitvity Platform will replace the legacy Desktop Productivity Platform anchored on Microsoft's Windows-MSOffice workgroup networking.  Just as Compound Documents were the fuel of desktop productivity apps and services, a new breed of compound documents will fuel cloud productivity based workgroups.  The article even demonstrates the basics of embedding charts, interactive feeds, media  and database streams in HTML5 document interfaces.  Still missing real time messaging between apps, but clearly the HTML5 cloud compound document model has arrived. excerpt: HTML5 will lead to richer mobile BI and CRM apps that can be used across browsers and devices. HTML has evolved considerably since it was first mapped out by Tim Berners-Lee more than 20 years ago. Now we're up to HTML 5.0, which could have a significant effect on the business intelligence and CRM landscape.
Gary Edwards

Google Launches Dart Programming Language - Development - Web Development - Informationweek - 1 views

www.informationweek.com/...231900449

Dart Google-DART JavaScript V8 Cloud-SQL

shared by Gary Edwards on 11 Oct 11 - No Cached
  • Gary Edwards on 11 Oct 11
     
    Google releases JavaScript alternative Web application programming language.  Release includes Cloud SQL, a cloud computing database to write Web apps against - using either JavaScript or DART. excerpt: Google on Monday introduced a preview version of Dart, its new programming language for Web applications. The introduction was widely expected, not only because the announcement was listed on the GOTO developer conference schedule, but because a Google engineer described the language and its reason for being in a message sent to a developer mailing list late last year. "The goal of the Dash [Dart's former name] effort is ultimately to replace JavaScript as the lingua franca of Web development on the open Web platform," said Google engineer Mark S. Miller in his post last year. More Insights White Papers The Dodd-Frank Act: Impact on Derivatives Technology Infrastructure Simple is Better: Overcoming the complexity that robs financial data of its potential Analytics Mobility's Next Challenge: 8 Steps to a Secure Environment SaaS 2011: Adoption Soars, Yet Deployment Concerns Linger Webcasts Effective IT Inventory and Asset Management: From Quagmire to Quick Fix Outsourcing Security: What Every Potential Cloud Security Customer Should Know Videos In an interview at Interop New York, Cisco's Justin Griffin shows how their wireless products can physically map radio sources by analyzing the spectrum. This allows you to detect rogue devices and sources of interference. Lars Bak, a Google engineer who helped develop Chrome's V8 JavaScript engine and one of the creators of Dart, said in a phone interview that Google works regularly on large Web applications and that the company's engineers feel they need a new programming language to describe large, complex Web applications.
Gary Edwards

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

www.winrumors.com/s-faster-than-previous-version

MS-Office2010 SharePoint Live.com MS-Cloud-Productivity

shared by Gary Edwards on 16 Jun 11 - No Cached
  • Gary Edwards on 16 Jun 11
     
    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.
  • Paul Merrell on 16 Jun 11
     
    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

Google's Enterprise Vision: Mobile First, In the Cloud - 0 views

www.readwriteweb.com/...les-enterprise-vision-mobi.php

cloud-computing cloud-productivity cloud-collaboration

shared by Gary Edwards on 12 Jun 11 - No Cached
  • Gary Edwards on 12 Jun 11
     
    Google "Innovation Nation" Conference in Washington, DC had an interesting conversation thread; that the move to Cloud Computing embraces a move for individual productivity to group productivity.  Not sure i agree with that.  The Windows Desktop-WorkGroup Productivity environment has dominated business since 1992.  Maybe Google might instead focus on the limited access of desktop workgroups and the fact that productivity was horribly crippled by the the PC's lack of communication.  The Web/Cloud magically combines and integrates communication with content and computation.  This is what makes cloud collaboration a genuine leap in productivity - no matter what the discipline.  Here's a question for Google: What's the productivity difference between desktop collaboration and cloud-collaboration? excerpt:  The meeting is the staple of corporate life. The whole day revolves around when a meeting will be, who will be there and what needs to be discussed. Yet, is this rote practice may have become counter-productive in today's world of the always on, always connected workplace. Google's enterprise vision is to leverage mobility and the cloud to change the fundamental way people work. Workforce productivity used to be about how you can optimize individual output. Take all those individuals, put their output together and have a meeting to sort it all out. Google thinks that by putting all that functionality into a cloud environment, workers can use whatever device they want and always be working as a group towards on the mission. A faster, more secure, more cost efficient workplace will be the result. "The main message is that to be an effective [enterprise], we need to change from individual productivity to group productivity,"
1 - 20 of 49 Next › Last »
Showing 20▼ items per page