Group items tagged

White paper from Intel discusses HTML5 and the future of computing. Intro: Computer programmers have been grappling with cross-platform issues since there was a second platform. Since then, the number of issues has rapidly increased. Today's developers can target at least four operating systems (plus their fragments), running on devices with all shapes, sizes, resolutions, persistence levels, input methods, carrier networks, connection speeds and states, UI conventions, app stores, deployment and update mechanisms, and on and on. Many of the world's developers once looked to Java* as the shining knight of cross-platform development. Indeed, the structured language of Sun* (and now Oracle) continues to solve many cross-platform issues. But it also introduces obstacles, not the least of which is a class structure that heavily burdens even the tiniest of program functions. Java's heft grew still more burdensome as developers turned to the browser for app delivery; Java applets are black boxes that are as opaque to the browser as the language is closed to the developer (with all due deference to the JCP). Around the same time Java was fuelling the browser wars, a like-named interpreted language was beginning to emerge. First called Mocha, later LiveScript, and finally JavaScript*, the language proved more useful than Java in some ways because it could interact with the browser and control content display using HTML's cascading style sheets (CSS). JavaScript support soon became standard in every browser. It is now the programming language of HTML5, which is currently being considered by the World Wide Web Consortium as the next markup-language standard. To better understand HTML5-why it is where it is and where it's going- Intel® Software Adrenaline turned to Moh Haghighat, a senior principal engineer in the Developer Products Division of Intel's Software and Services Group. Moh was the technical lead from Intel's side on the first JavaScript

Despite initial comments in support of HTML5 as an option standard, Adobe has taken action to sabotage the open specification in an effort to support its existing position with Flash. Ian Hixie, a member of the HTML5 working group and an employee of Google, reported this week that "the latest publication of HTML5 is now blocked by Adobe, via an objection that has still not been made public (despite yesterday's promise to make it so)."

CloudStack Manifesto Before getting into the framework specifics, it would be worthwhile to cover some of the design principles we had in mind while we were building CloudStack: CloudStack brings together the best of the web and the desktop: We strongly believe in the convergence of the desktop and the web and will continually strive to expose more services that bring out the best from both. CloudStack enables rapid application development and deployment: Out of the box, CloudStack provides a fully brand able and deployable shell application that can be used as a starting point to jumpstart application development. CloudStack also provides a scalable deployment environment for hosting your applications. CloudStack leverages existing web technologies: We built the CloudStack P2WebServer container over the J2EE compliant Jetty web server. As a result, CloudStack applications are built using standard web technologies like AJAX, HTML, JavaScript, Flash, Flex, etc. CloudStack does not reinvent the wheel: We strive to reuse as much as possible from other open source projects and standards. By creatively stringing together seemingly disparate pieces, like P2P and HTTP, it?fs amazing to create something that's really much greater than the sum of the parts. CloudStack does aim to simplify existing technologies: We will abstract and simplify existing interfaces if needed. For example, we built simpler abstractions for JXTA (P2P) and Jena (RDF Store). CloudStack encourages HTML-based interfaces: We believe that the web browser is the most portable desktop application container with HTML being the lingua franca of the web. Rather than writing a native widget interface for the local desktop application and another web-based interface for the remote view, we encourage writing a single interface that can be reused across both local and remote views. HTML based interfaces are inherently cross-platform and provide good decoupling of design from code (versus having the UI as compiled

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.

Jonathan Deutsch and Ryan Nielsen left Apple late last year to join Y Combinator's accelerator program and help designers build animations in HTML5 as opposed to Flash. Friday, the two-man team is releasing Hype, the first product of their startup Tumult, on the Mac App Store. Hype, which sells for $29.99, uses WebKit to render pages and has been crafted so that anyone comfortable with using Keynote or PowerPoint can start building animations in HTML5, no code required. "It's pretty clear that HTML5 is the future of the web," says Deutsch. "It will, of course, run not only on desktop machines but also runs really well on any modern smartphone or tablet like the iPad. The problem is that there are no good designer apps for creating animated HTML5 like there are for Flash." Hype presents the user with a blank canvas with a timeline at the bottom. The user can then drag in images, video and text, arrange those elements and use keyframe-based animations to define where those pieces of content go.

While HTML5 developers are working directly with JavaScript, SVG, CSS, and other technologies, Flash designers enjoy a high-level environment with timelines, drawing tools, easy control of animation effects, and more. With Edge, released in beta Sunday, Adobe is striving to bring that same ease of use to HTML5 development. The user interface will be familiar to anyone who's used Flash or After Effects; a timeline allowing scrubbing and jumping to any point in an animation, properties panels to adjust objects, and a panel to show the actual animation. Behind the scenes, Edge uses standard HTML5. Scripting is provided by a combination of jQuery and Adobe's own scripts, and animation and styling uses both scripts and CSS. Pages produced by Edge encode the actual animations using a convenient JSON format. Edge itself embeds the WebKit rendering engine-the same one used in Apple's Safari browser and Google's Chrome-to actually display the animations.

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

"HTML5, the latest version of the language of the Web, was designed with Web applications in mind. It contains a slew of new application programming interfaces (APIs) designed to allow the Web developer to access device hardware and software using JavaScript. Some of the more exciting HTML5 specifications include the following: Geolocation API lets the browser know where you are Media Capture API lets the browser access your camera and microphone File API lets the browser access your file system Web Storage API lets Web applications store large amounts of data on your computer DeviceOrientation Event Specification lets Web apps know when your device changes from portrait to landscape Messaging API gives the browser access to a mobile device's messaging systems Contacts Manager API allows access to the contacts stored in a user's contacts database"

Another HTML5 Application Platform for Cloud Computing.  Provides secure data connections to existing business systems and workflows.  Not an Open Web Platform. summary: Mobile Helix is an enterprise application and data security platform provider focused on enabling unrestricted enterprise productivity. We are redefining endpoint computing by evolving and extending existing IT infrastructure and standards rather than reinventing them. At our core are three fundamental principles that are at the center of everything that we do: 1) we are application- and data-centric - we embrace the blurring lines between phones, tablets and laptops, permitting IT to relinquish control of the endpoint device entirely and embrace a bring-your-own-anything policy; 2) we provide unmatched yet unobtrusive security for sensitive corporate data by intelligently securing the data rather than the devices; and 3) simplicity is embedded into the DNA of our products, our designs and our communications. Our solution, Mobile Helix Link, is the industry's first pure HTML5 platform that combines unparalleled data security, a unique HTML5 application development and delivery platform, and breakthrough patent-pending performance enhancement technology. 

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+

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

Thankfully, there's buddying technology to block computer facial-recognition algorithms. http://tinyurl.com/mzfyfra On the other hand, used Hallowe'en masks can usually be purchased inexpensively from some nearby school kids at this time of year. Now if I could just put together a few near-infrared LEDs to fry a license plate-scanner's view ...  

Excellent but light weight and breezy review of the Flash-Silverlight-Open Web HTML5 battle for the future of the Web. excerpt: At the top of the org chart, Apple's deprecation of Flash technology is all about politics. Apple doesn't want its mainstream video delivery system controlled by a third party. So Mr. Jobs backs up his politics with tidbits of technical truths. However, discovering the real truths about HTML5 and Flash is a bit harder, as this survey shows. On February 11th, I wrote an editorial, "What Should Apple Do About Adobe?" Part of the discussion related to Adobe's Flash Player on the Mac, updates and security. Inevitably, the comments escalated to a discussion of Steve Job's distaste for and blocking of Flash on the iPhone and iPad. The question is: is Apple's stance against Flash justified? Of course, any political argument needs only the barest of idealogical arguments to sustain itself. More to the point is, can Apple fight this war and win based on the state-of-the-art with HTML5? Again, Apple's CEO must believe he can win this war. There has to be some technical basis for that, or the war wouldn't be waged.

Excellent review of Windows 8, including some prescient thinking about what it means to have HTML+ Web Apps running natively on the Win8 OS platform.  The author/reviewer Sebastion Anthony suggest why this breakthrough is a problem for Google, Apple and Mozilla.  I'm wondering though; is this a problem for the Open Web future?  Or is this a positive step towards an Open Web communications and collaborative computation platform that  is used by all and owned by none?   After nearly thirty years of a love-hate-hate more than ever relationship with Microsoft, for sure Win8 and native HTML+ is something to carefully watch.

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.

Chrome runs as close as any browser can to the bleeding edge of Web standards. Though it uses the same open source WebKit rendering engine as Safari, it doesn't reliably support the controversial, proprietary CSS3 transformation and animation tricks that Apple's built into Safari. However, like every browser I tested, it earned a perfect score in a compatibility test for CSS3 selectors, and it joined Safari and Opera with a flawless score of 100 in the Acid3 web standards benchmark. Chrome 5 also supports both Apple's H.264 codec and Mozilla's preferred open source Ogg Theora technology for plugin-free HTML5 video, and it beautifully played back HTML5 demo videos from YouTube and Brightcove. In XHTML and CSS tests, Chrome was surprisingly slower than Safari, despite their shared rendering engine -- but the race was close. Safari rendered a local XHTML test page in 0.58 seconds to Chrome's 0.78 seconds, and a local CSS test page in 33 milliseconds to Chrome's 51 milliseconds. Note that Chrome still rendered XHTML more than twice as fast as Opera (1.67 seconds) and left Firefox (12.42 seconds--no, that's not a typo) eating its dust. In CSS, it also beat the pants off Opera (193 milliseconds) and Firefox (342 milliseconds). But Chrome shines brightest when handling JavaScript. Its V8 engine zipped through the SunSpider Javascript benchmark in 448.6 milliseconds, narrowly beating Opera's 485.8 milliseconds, and absolutely plastering Firefox's 1,161.4 milliseconds. However, Safari 5's time of 376.3 miliseconds in the SunSpider test beat Chrome 5 handily.