Group items tagged

Quick overview of HTML5 document structures and how to implement them.

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.

Wow.  Does this mean i no longer have to create URL links in my documents?  With this Aperture-Scribd agreement, everything is linked automagically.  Everything!  So, here's the news blip, "the document-sharing site Scribd will now allow users to use Apture Highlights on the tens of millions of public documents posted on the content platform. 'Apture Highlights' plugs the "search leak" that is taking place with content on the web. The feature allows you to highlight any word or phrase on a page and instantly bring up search results in a window. The startup brings results from 60-plus sources including YouTube, Twitter, Wikipedia, Google and more for extra context around content. Now, when users are reading documents, books, or other works on Scribd, they will be able to highlight any word, and Apture will open a small browser within the page to search for the additional information on Google, Bing or Yahoo. Scribd representative Michelle Laird said that this integration is made possible party because of the company's move to convert the platform to HTML5.  I guess this means that hyperlinking that made the World Wide Web such an exciting and ultimately dominant Internet application, has moved to a new level of auto linking.  Is there an anchor tag in HTML5 i can use to point the mega search engines first at the primary research, then to wikipedia, and then to the global search list?

In depth technical discussion about Flash, HTML5, H.264, and Google's VP8.  Excellent.  Read the comments.  Bottom line - Google has the juice to put Flash and H.264 in the dirt.  The YouTube acquisition turns out to be very strategic. excerpt: The internet has been filled for quite some time with an enormous number of blog posts complaining about how Flash sucks-so much that it's sounding as if the entire internet is crying wolf.  But, of course, despite the incessant complaining, they're right: Flash has terrible performance on anything other than Windows x86 and Adobe doesn't seem to care at all.  But rather than repeat this ad nauseum, let's be a bit more intellectual and try to figure out what happened. Flash became popular because of its power and flexibility.  At the time it was the only option for animated vector graphics and interactive content (stuff like VRML hardly counts).  Furthermore, before Flash, the primary video options were Windows Media, Real, and Quicktime: all of which were proprietary, had no free software encoders or decoders, and (except for Windows Media) required the user to install a clunky external application, not merely a plugin.  Given all this, it's clear why Flash won: it supported open multimedia formats like H.263 and MP3, used an ultra-simple container format that anyone could write (FLV), and worked far more easily and reliably than any alternative. Thus, Adobe (actually, at the time, Macromedia) got their 98% install base.  And with that, they began to become complacent.  Any suggestion of a competitor was immediately shrugged off; how could anyone possibly compete with Adobe, given their install base?  It'd be insane, nobody would be able to do it.  They committed the cardinal sin of software development: believing that a competitor being better is excusable.  At x264, if we find a competitor that does something better, we immediately look into trying to put ourselves back on top.  This is why

Very detailed and well organized discussion comparing HTML5, Flash and Silverlight. excerpt intro: Over the past week, I had a slew of press inquiries about the future of Flash, driven largely by the Apple iPad announcement - an event in which Flash was conspicuously absent. Of the top of my head, I put together some key points in the conversation, presented below. As I mull these talking points over and discuss them with colleagues, some of these will likely end up in a research note, along with actionable advice. For now, here are some aspects of a multi-faceted situation.

I left a lengthy comment on this very good article. excerpt: According to the latest study from Juniper Research, the market for cloud-based mobile applications will grow 88% from 2009 to 2014. The market was just over $400 million this past year, says Juniper, but by 2014 it will reach $9.5 billion. Driving this growth will be the adoption of the new web standard HTML5, increased mobile broadband coverage and the need for always-on collaborative services for the enterprise. Cloud Apps in your Pocket Mobile cloud computing is a term that refers to an infrastructure where both the data storage and the data processing happen outside of the mobile device from which an application is launched. To the typical consumer, a cloud-based mobile application looks and feels just like any app purchased or downloaded from a mobile application store like iTunes. However, the app is driven from the "cloud," not from the handheld device itself. There are already a few well-known mobile cloud apps out there including Google's Gmail and Google Voice for iPhone. When launched via iPhone homescreen shortcuts, these apps perform just like any other app on the iPhone, but all of their processing power comes from the cloud. In the future, there will be even more applications like these available, but they won't necessarily be mobilized web sites like those in Google's line-up. Cloud-based mobile apps are perfectly capable of being packaged in a way that allows them to be sold alongside traditional mobile apps in mobile application stores, with no one but the developers any wiser. HTML5 Paves the Way for Mobile Web's Future

Open Source framework for building visually-immersive mobile ready magazines in HTML5-CSS3-JavaScript. excerpt:  Pugpig is an open source framework that enables you to publish HTML5 content in the form of a magazine, book or newspaper to iPhone and iPad devices. It's slick and feels like you are using a native app (we tested the it on the iPad) Pugpig is an HTML reader for iOS. It's basically a hybrid - part native application, part web app, designed to prove that you can have an HTML-based app that feels like it's native. Your app sits on top of the Pugpig framework. It can be customized and extended. For example, you can link to your own data source, change the navigation and look and feel. It can also be multi-lingual - for example, the sample app I tested leverages the AJAX API for the Microsoft Translator. Additional Pugpig benefits are its low memory footprint and ability to store a lot magazine/newspaper editions within the device, for easy offline viewing. You can offer your app in either the App Store or the new iOS 5 Newsstand (integration with the framework is in progress now).

Modernizr is a new library that detects various HTML5 and CSS3 features and lets you know so you can use them: Enables the writing of conditional CSS and conditional JavaScript! The JS tools just keep coming.

You need an HTML5 ready browser to visit this demonstration.  Amazing stuff though.  The latest Chrome beta 3.0.196.2 works well.  Ajaxian has a review of this at:  http://ajaxian.com/archives/audio-canvas Lots of Webkit tweets in the demo!

HTML5 development company appMobi is releasing a new browser today called MobiUs that will give mobile Web apps the same type of functionality that now is currently only enjoyed by native apps for platforms like iOS and Android. AppMobi thinks of MobiUs as the replacement for Flash in mobile - it renders mobile websites like a Flash extension would and gives developers device access in ways previously unavailable to in HTML5. MobiUs is technically a mobile browser. That is not the way appMobi thinks it will be used though. The company expects it to be function more like a browser extension. Like Flash, users will be prompted to download it once and from then it will just run in on the device.

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+

HTML5 app development resource and advice site.  Same people who did the excellent CSS3 Please site.

Good article covering lots of JavaScript Libraries and their specific uses. excerpt:  Over drinks, one person proclaimed, "No one programs in JavaScript, they just string together jQuery calls." This statement is certainly not true, but like a hand grenade, it gets close enough to make its point. jQuery sure seems to be everywhere, and with good reason: Its creators took all of the neat ideas from libraries like Prototype, Dojo, and Yahoo's YUI, then turned them into something that was just a tad easier to use. When jQuery nurtured fertile plug-in culture, the library became irreplaceable. One seemingly random estimate claimed that at least 70 percent of JavaScript is jQuery. While there is probably no scientific way to make such a blanket statement, the fact that someone would try is good enough.