Their intent was to talk their clients away from using HTML5 for data visualization projects in favor of the still dominant Flash. They also have a side-comparison to iOS usage—I assume to show that developing iPhone Apps is also not their preference.
What I like about this infographic though is that it shows very well that Flash is far from dead, and it should remain an option to be considered for specific projects with specific audiences. But as with any project you must know Flash’s weaknesses in order to know when to use it and when not to.
The same, of course, can be said for HTML5 and iOS apps.
The web continues to be in turmoil when it comes to standards and best practices (no thanks to Microsoft and Internet Explorer). Flash is…
Came across this blog post this past weekend:
CSS is the new Photoshop
It’s talking about CSS3 and HTML5’s ability to render graphic elements with absolutely no images involved. The benefit being that you have fewer calls to the server to retrieve images (why CSS sprites have become popular).
The print guys can think of it like Illustrator vs Photoshop. This new process doesn’t use pixels (like Illustrator). Where Photoshop pixels have the overhead of downloading from the server, these can render within the browser itself.
Nested several links deep it gets to this CSS Images example page (requires the latest Safari or Chrome):
It’s not necessarily the slimmest HTML out there (you can see how they…
One would think that when you clone a group of form fields and populate them elsewhere in the DOM that the values of the form fields would be populated correctly as well. Not neccesarily. Especially when dealing with the ever frustrating Internet Explorer.
I recently had to develop a page that contained a dynamically built form based on values received from a web service. We decided to use ajax to post the form data to the server. With JQuery, posting a form using ajax is very simple and easy. You serialize the form and post it to the processing page like this:
var formdata = $(’#holdingForm’).serialize();
$.post(“ajax/updateIntegrationProvider.aspx?pid=” + prvdrID, formdata, ajaxResponse, “text”);
However when using .NET, the…0 comments
HTML5 is the buzz all of a sudden… Google (especially the upcoming Google Wave...and Google Docs) is pushing it really hard.
HTML5 is largely backwards compatible so long as it’s new features are coded in a way that allows it to degrade well… All the new functionality could be lost if the user’s browser doesn’t understand HTML5, but if you build knowing that, we may be able to use parts of it to provide a better experience for users who are up-to-date.
Firefox 3.5 just came out with robust support for HTML5. Safari 4 came out a while back with decent support for it. Google Chrome I hear has decent support (surprised they don’t have the best support…).
Here’s an interesting article explaining the differences: