The new Android 2.2-powered Optimus series. A small diversion from WebKit discussion, but does it not drive anyone else crazy that Android devices don’t have a consistent order for the four hardware buttons under the screen?
The new Android 2.2-powered Optimus series. A small diversion from WebKit discussion, but does it not drive anyone else crazy that Android devices don’t have a consistent order for the four hardware buttons under the screen?
Yes, the marquee tag may feel a bit tacky — reminiscent of the blink tag, but I think it does have a place in certain contexts, like with overflow, nowrap text.
A Message to the Palm Developer Community
HP Chief Technology Officer Phil McKinney joins Ben Galbraith and Dion Almaer from the Palm Developer Relations Team to discuss what the future looks like for webOS developers.
Article on Drawar:
Imagine the headaches Microsoft would get rid of by using WebKit. No longer could we blame IE for our development headaches. We could test a site in IE, Chrome or Safari and there is a good chance if it works in one that it will work in the other two. That sounds like bliss to me.
There’s one point I’d like to add to this argument: Standardizing on a rendering engine such as WebKit does not mean innovation has to be stifled. Chrome uses WebKit and still has plenty of differentiation with Safari. Its V8 Javascript engine, for one, is entirely custom and known for its remarkable performance. Browsers like IE and Firefox could learn something here — what if IE were to take a build of WebKit, build in Silverlight, and make great use of it in the browser’s default pages?
I realize that WebKit isn’t perfect and there are way too many versions of it out there, but still, as I’ve mentioned before — it’s an open source project working against a standard. It’s used for over 90% of mobile browsing (or will be soon). Browser makers like Microsoft and Mozilla should swallow their pride, take the unique features they’ve each brought to their respective browsers, and start figuring out how to develop them on top of WebKit — it’s the quickest way for web development to move forward as a whole.
Todd Dominey announces SlideShowPro Mobile:
SlideShowPro Mobile is an entirely new media player built using HTML5 that doesn’t require the Flash Player plugin and can serve as a fallback for users accessing your web sites using these devices. But it’s not just any fallback — it’s specially designed for touch interfaces and smaller screen sizes. So it looks nothing like the SlideShowPro player and more like a native application that’s intuitive, easy to use, and just feels right.
Jeremy Keith takes a look at HTML5 audio support and a clever trick for using mp3s cross-browser.
Gangsta Ass CSS3 Wrapping Drop Shadows
Better & leaner than the previous example CSS Drop Shadow, although as with the previous example, it does break if the width is too great..
Thanks to Paul Irish for bringing this to my attention
2009–2010 David Kaneda