Skip to main content

Home/ Open Web/ Group items tagged Application

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

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

www.zdnet.com/d-tools-gain-ground-7000022114

Office-Productivity Cloud-Computing Cloud-Productivity-Platform Cloud-Compound-Document HTML5

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

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

How to Jailbreak iOS 4.0 for iPhone 3G - 0 views

www.readwriteweb.com/...break_ios_40_for_iphone_3g.php

iPhone jailbreak iPhone4

shared by Gary Edwards on 25 Jun 10 - Cached
  • Gary Edwards on 25 Jun 10
     
    Jailbreaking vs. Unlocking Jailbreaking and unlocking the iPhone are two different hacks which allow you to take control of your mobile device in different ways. Jailbreaking is a type of hack that lets you install unapproved third-party applications on your iPhone or iPod Touch from searchable repositories provided by apps like Cydia and Icy. Unlocking, on the other hand, is a hack that lets you use your iPhone on another cellular network. Here in the U.S., that means you can use the iPhone on T-Mobile instead of AT&T. You have to first jailbreak your phone before you can unlock it, but you don't have to unlock a phone in order to jailbreak it. How to Jailbreak the 4.0 Software for the iPhone 3G and iPod Touch Second Generation The "Redsn0w" jailbreak software has been updated to support iOS 4.0 on both Mac and Windows and works for iPhone 3G and the iPod Touch, second generation. This jailbreak is especially helpful for for iPhone 3G owners as the new OS won't offer the much sought-after multitasking feature on their devices. A jailbreak application called multifl0w will, however, provide an alternative. Another jailbreak app called WinterBoard offers a way to customize the iPhone's background even though that too is disabled for 3G owners running the latest OS 4.0 update. This jailbreak guide assumes you've already downloaded and updated your phone or iPod Touch to the latest software, iOS 4.0, and have backed up your device. If you are looking to unlock your phone in order to run it on a network belonging to another carrier, this is not the guide for you.
Paul Merrell

Google Sites API opens Microsoft SharePoint - Techworld.com - 1 views

news.techworld.com/...api-opens-microsoft-sharepoint

Google Sharepoint Lotus Notes Google Sites

shared by Paul Merrell on 30 Sep 09 - Cached
Gary Edwards liked it
  • Signaling an intent to compete with giants in the collaboration software space, Google unveiled an API to extend the Google Sites collaborative content development tool, featuring a capability to migrate files from workspace applications such as Microsoft SharePoint and Lotus Notes to Sites. One application already built using the Google Sites API is SharePoint Move for Google Apps, developed by LTech for migrating data and content from SharePoint to Sites. Google Sites is a free application for building and sharing websites; it is described by Google as a collaborative content creation tool to upload file attachments, information other Google applications such as Google Docs, and free-form content.
Gary Edwards

Reinventing Copy and Paste - Anil Dash - 0 views

dashes.com/...reinventing-cop.html

web-productivity-platform

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

Thousands of HTML5 tests planned by Web consortium - 0 views

www.networkworld.com/...113010-html5-tests.html

W3C html5 test suite

shared by Paul Merrell on 02 Dec 10 - No Cached
  • W3C is warning against drawing any conclusions based on the early tests, saying thousands of more HTML5 tests are planned. The goal of the tests is not to declare one browser a winner, but rather to help vendors and Web application developers ensure interoperability across all browsers, W3C says.
  • "We do expect to have tens of thousands of tests," says Philippe Le Hegaret, who oversees HTML activities for the W3C. 
  • the purpose of the HTML5 test suite is to help vendors and developers ensure that HTML5 applications work across all browsers. For example, a developer might check the test results before enabling a certain feature in an application, just to make sure it will work across IE9, Firefox, Chrome, Safari and Opera. Developers can build HTML5 applications today, but they have to keep in mind that they are early adopters and act accordingly, Le Hegaret says. "If you think HTML5 is perfectly stable today and you can use it without worrying about interoperability issues, I think you're going to fool yourself," he says. Although the first round of HTML5 tests focused on desktop browsers, Le Hegaret says HTML5 compatibility is advancing more rapidly on mobile devices such as iPhones and Androids.
    • Paul Merrell
      Paul Merrell on 02 Dec 10
       
      Note the continuing, indeed, escalating abuse of the term "interoperability" by W3C. "Interoperability" has both a legal and (happily, coinciding) technical meaning that involves round-tripping of information. ISO/IEC JTC 1 Directives defines the term in precisely the same terms as the European Union's Court of First Instance did in the landmark Commmission v. Microsoft antitrust case; "interoperability is understood to be the ability of two or more IT systems to *exchange* information at one or more standardised interfaces and to make *mutual use* of the information that has been exchanged." Web browsers do not do "interoperability;" there is no "exchange" and "mutual use" of the information exchanged. Web browsers do "compatibility," a one-way transfer of information that is broadcast from web servers; i.e., web browsers cannot send web pages to web servers.
Gary Edwards

Munich administration switches to OpenDocument Format - The H Open Source: News and Fea... - 0 views

www.h-online.com/...penDocument-Format-895415.html

munich documents

shared by Gary Edwards on 05 Jan 10 - Cached
  • Gary Edwards on 05 Jan 10
     
    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.
Gary Edwards

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

www.labnol.org/...11403

Microsoft-Cloud BPOS SkyDrive gDocs

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

A Humbled Microsoft Opens Windows to Rivals - TIME - 1 views

www.time.com/...0,8599,1948381-1,00.html

ge Open-Web Open-Web-Ecosystem BPOS browsers microsoft-monopoly

shared by Gary Edwards on 17 Dec 09 - Cached
  • Gary Edwards on 17 Dec 09
     
    excerpt: "Once upon a time, Microsoft bestrode the software world like a ruthless cartoon villain, gobbling up rivals and defying pleas for restraint from regulators. But the once-impregnable giant has now been humbled: following an acrimonious 10-year anti-trust battle with European regulators, Microsoft on Wednesday finally agreed to open its Windows operating system to rival web browsers in Europe." Great opening line!  But they get the story wrong.  Woefully wrong!  Just the opposite is happening.  Microsoft has moved from the browser Web application to the Web itself.  It's the platform stupid!!! No one understands platform better than Microsoft.  Control the platform's base formats, protocols, interfaces and internal messaging system, and you control all applications, services and devices using that platform.   The problem for Microsoft has been that the Web is a platform used by all, but owned by none.  It's based on open standards that no one owns or controls.  So as the Web evolves into a universal platform for converged communications, content and collaborative computing, Microsoft was facing the one fate every monopolist fears - having to compete on a level playing field! While it took them well over ten years to come up with a counter strategy and effective implementation, Microsoft has finally achieved the impossible.   They have carved out a huge section of the Open Web for their proprietary and exclusive use.  
Gary Edwards

Topix Weblog: The Secret Source of Google's Power - 1 views

blog.topix.com/...000016.html

google platform

shared by Gary Edwards on 20 Apr 10 - Cached
  • Gary Edwards on 20 Apr 10
     
    Incredible.  Despite the title.  It's the platform stupid! excerpt: Much is being written about Gmail, Google's new free webmail system. There's something deeper to learn about Google from this product than the initial reaction to the product features, however. Ignore for a moment the observations about Google leapfrogging their competitors with more user value and a new feature or two. Or Google diversifying away from search into other applications; they've been doing that for a while. Or the privacy red herring. No, the story is about seemingly incremental features that are actually massively expensive for others to match, and the platform that Google is building which makes it cheaper and easier for them to develop and run web-scale applications than anyone else. I've written before about Google's snippet service, which required that they store the entire web in RAM. All so they could generate a slightly better page excerpt than other search engines. Google has taken the last 10 years of systems software research out of university labs, and built their own proprietary, production quality system. What is this platform that Google is building? It's a distributed computing platform that can manage web-scale datasets on 100,000 node server clusters. It includes a petabyte, distributed, fault tolerant filesystem, distributed RPC code, probably network shared memory and process migration. And a datacenter management system which lets a handful of ops engineers effectively run 100,000 servers. Any of these projects could be the sole focus of a startup.
Gary Edwards

Owe Someone Money? Just Bump Your Phones - NYTimes.com - 0 views

bits.blogs.nytimes.com/...ne-money-just-bump-your-phones

Bump PayPal mobile-computing

shared by Gary Edwards on 12 Jan 11 - No Cached
  • Gary Edwards on 12 Jan 11
     
    Good explanation of how Bump and PayPal work together. People have predicted the death of cash and checks for a long time. But there are certain transactions - like paying a friend back for dinner or buying vegetables at the farmers' market - for which they remain essential. ¶PayPal's new iPhone application could finally change that. It promises to let you quickly divide a restaurant bill and send a friend the portion you owe just by bumping your iPhones together. ¶The application is free to download from the App Store. Users log in with their PayPal credentials or with their cellphone number and a numeric PIN, and they can send or request money and manage their account on the phone. ¶To send money, users choose a recipient from their cellphone contacts or bump two phones together. For that, the app uses technology from Bump Technologies, which developed it to swap contact information between two phones. The money is transferred immediately
Gary Edwards

I Want To Build A Website. Do I Need a Content Management System (CMS)? - www.htmlgoodi... - 2 views

www.htmlgoodies.com/...3887866

HTML5 Drupal Mobility CMS Sursen

shared by Gary Edwards on 15 Jan 11 - No Cached
  • Gary Edwards on 15 Jan 11
     
    Although there are many open source CMSes available, we're going to focus on those that are based upon PHP. The following CMSes are thus PHP-based, and use a MySQL database. The advantages of using such a CMS include portability, support and a large developer base with frequent updates and improvements. We will discuss the following four CMSes: Drupal - a free open source content management system written in PHP and distributed under the GNU General Public License Joomla - an open source content management system platform for publishing content as a Model-view-controller (MVC) web application framework PHPNuke - a web-based automated news publishing and content management system based on PHP and MySQL Wordpress - an open source CMS, often used as a blog publishing application, and is the most popular blog software in use today
Gary Edwards

Amazon SDKs Boost Support for Mobile Cloud « Data Center Knowledge - 0 views

www.datacenterknowledge.com/...oosts-support-for-mobile-cloud

sursen cloud-computing amazon-sdk

shared by Gary Edwards on 17 Jan 11 - No Cached
  • Gary Edwards on 17 Jan 11
     
    Amazon Releases Developer SDKs One interesting and important exception is Amazon's recent release of its Software Development Kits (SDK) for Google's Android and Apple's iOS. With these kits, developers are provided with tools that will simplify development of cloud applications stored on the Amazon Web Services cloud platform, or AWS. Developing apps that can use many of the already popular AWS cloud services offers many new opportunities for the developer community, especially due to its low-barrier-to-entry and affordability, enabling more developers with limited resources  to build and provision new mobile cloud services. The new SDK includes libraries that simplify handling of HTTP connections, request retries and error handling, which used to be complex and arduous. Integration of applications with several AWS cloud services, like the Simple Storage Service (S3), SimpleDB database, Simple Notification Service (SNS) and Simple Queue Service (SQN) will be much more accessible than before. For example, it's going to be interesting to see whether developers will build a viable messaging solution atop the AWS SNS service that can actually compete with mobile SMS services - which have been a long-time major cash-cow for many mobile network operators.
Gary Edwards

WYMeditor - web-based XHTML editor - Home - 2 views

www.wymeditor.org

WYMeditor RTE Rich-Text-Editors NoteCasePro

shared by Gary Edwards on 18 Jan 11 - Cached
  • Gary Edwards on 18 Jan 11
     
    WYMeditor is a web-based WYSIWYM (What You See Is What You Mean) XHTML editor (not WYSIWYG). WYMeditor's main concept is to leave details of the document's visual layout, and to concentrate on its structure and meaning, while trying to give the user as much comfort as possible (at least as WYSIWYG editors). WYMeditor has been created to generate perfectly structured XHTML strict code, to conform to the W3C XHTML specifications and to facilitate further processing by modern applications. With WYMeditor, the code can't be contaminated by visual informations like font styles and weights, borders, colors, ... The end-user defines content meaning, which will determine its aspect by the use of style sheets. The result is easy and quick maintenance of information. As the code is compliant to W3C XHTML specifications, you can for example process it using a XSLT (at the client or the server side), giving you a wide range of applications. ...................... Great colors on this Web site!  They have mastered the many shades of Uncle Ten's (the Chinese Brush Master, James Liu) charcoal blue
Gary Edwards

2011 Will be the Year For Mobile in APAC - 0 views

www.cmswire.com/...-for-mobile-in-apac-009959.php

sursen cloud-computing APAC

shared by Gary Edwards on 26 Jan 11 - No Cached
  • Gary Edwards on 26 Jan 11
     
    APAC=Asian Pacific markets Meanwhile, the popularity of smartphones and tablets is expected to give rise to mobile cloud applications. In effect, going to the cloud will help smartphones and tablets overcome inherent hardware limitations, such as small storage, inadequate processing speed and power-saving requirements. Mobile security will also be a prime concern, especially for enterprise users. This will include safety and privacy applications like remote wipe and virus protection. Nitin says that the market for cloud computing in APAC has grown to US$ 1.1 billion this year, which is mostly comprised of SaaS deployments. He highlights the role of Singapore as a cloud computing hub in the region, given a strong broadband infrastructure and the presence of a large base of multinational companies.
Gary Edwards

Ericom Launches Pure HTML5 RDP Client -- Campus Technology - 0 views

campustechnology.com/...hes-pure-html5-rdp-client.aspx

Ericom AccessNow HTML5-RDP cloud-computing

shared by Gary Edwards on 09 Jun 11 - No Cached
  • Gary Edwards on 09 Jun 11
     
    Wow!  This reads like a premature press release, but if true it's breakthru technology.  I wonder though why Ericom is targeting education?  Seems this innovation would be of immediate importance to enterprise and SMB businesses struggling with the great transition from desktop/workgroup productivity systems to Web Productivity Platforms. excerpt: Ericom has released AccessNow, a pure HTML5 remote desktop (RDP) client that runs within a Web browser without the need to install anything on the client device. AccessNow provides accelerated remote access to applications and desktops running on Windows Terminal Services, remote desktop services (RDS), and virtual desktop infrastructure (VDI), including applications, remote desktops, VMware View desktops, virtual desktops running on Microsoft Hyper-V, and other hypervisors. AccessNow works on any device with an HTML5-capable browser, such as Chrome, Safari, Firefox, Opera, and others, without the use of browser plugins, Java, Flash, ActiveX, Silverlight, or other underlying technology. Internet Explorer is also supported, although it does require the Chrome Frame plugin. AccessNow uses only the standard Web technologies: HTML, CSS, and JavaScript. This approach helps IT administrators maintain centralized control of school resources. It also enables students and staff to use any Internet-enabled device, including smartphones, tablets, and Chromebooks, to do their work anywhere and anytime.
Gary Edwards

HTML5 Can Get the Job, But Can HTML5 Do the Job? - 2 views

www.readwriteweb.com/...l5-can-get-the-job-but-can.php

HTML5 mobile-apps HTML+ HTML-CSS-JavaScript OpenWeb-Productivity-Platform Cows

shared by Gary Edwards on 09 Aug 11 - No Cached
  • Gary Edwards on 09 Aug 11
     
    Great chart and HTM5 App development advice from pinch/zoom developer Brian Fling!   excerpt: In a post on pinch/zoom's blog Swipe, Fling discusses the "Anatomy of a HTML5 Mobile App" and what developers will need to get started, what the pitfalls are and why HTML5 is so difficult. HTML5 is a lot like HTML, just more advanced. Fling says that "if you know HTML, then chances are you'll understand what's new in HTML5 in under an hour." Yet, he also says that HTML5 is almost nothing without Javascript and CSS. Device detection, offline data, Javascript tools, testing, debugging and themes are issues that need to be resolved with the tools at hand. One of the big challenges that developers face is the need to fully comprehend Javascript. That starts from the most basic of codes on up. Fling says that many developers cannot write Javascript without the aid of frameworks like Prototype, MooTools, jQuery or Scriptaculous. That would not be so much of a problem if all an application consisted of was functionality and theme, but the data and multiple device requirements of apps and working with the HTML5 code means that troubleshooting a Web application can be extremely difficult if a developer does not know what to look for in Javascript. Fling breaks down the three parts of the Javascript stack that is required in building HTML5 apps - hybrid, core and device scripts. Then there is CSS. Fling likens CSS to the make, model, interior and attention to detail of a car. "Javascript definitely influences our experience as well, but they are the machinations out of view," Fling wrote. "We absolutely need it to be there, but as any Top Gear fan can tell you - power under the hood doesn't always equal a powerful experience." So, HTML5 can get the job. But can it do the job? Fling says yes, but with these caveats:
Gary Edwards

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

industry.bnet.com/...s-ecosystem-changes-everything

Web-Productivity-Environment Open-Web MS-Web MSOffice-ecosystem Open-Web-Ecosystem Open-Web-Productivity

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

Zoho Office For Microsoft SharePoint, Online Collaboration, Online Word Processor, Onli... - 0 views

www.zoho.com/sharepoint

zoho-sharepoint on-line-editing office20 collaboration

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

Google shows Native Client built into HTML 5 - ZDNet.co.uk - 0 views

news.zdnet.co.uk/...0,1000000097,39657632,00.htm

wave html5 html gwt O3D web-workers google

shared by Gary Edwards on 02 Jun 09 - Cached
  • Gary Edwards on 02 Jun 09
     
    Good article from Stephen Shankland describing how the Wave-HTML5-O3D-Web Worker pieces fit. He left out GWT. But this after all, one very big picture. Google has thrown down a game changer. Wave represents one of those rare inflection points where everything immediately changes. There is no way to ignore the elephant that just sat on your face. Google has been demonstrating its sandboxing technology for making web applications perform at similar levels to those associated with native desktop applications. Google Native Client, still highly experimental, lets browsers run program modules natively on an x86 processor for higher performance than with web-programming technologies, such as JavaScript or Flash, that involve more software layers to process and execute the code. But to use it, there is a significant barrier: people must install a browser plug-in.
« First ‹ Previous 61 - 80 of 264 Next › Last »
Showing 20▼ items per page