Archive for December, 2011

File Under: Web Services

Google Easter Egg Brings a White Christmas to Your Web Browser

Google offers up some frosty search results

If you’re still waiting for winter to arrive, Google can help. The search engine might not be able to bring you a white Christmas outside, but it can at least add some snow to your web browser. A recently uncovered Easter egg uses JavaScript to bury your search results under a fresh coat of snowy pixels.

To see the hidden feature just head to Google.com and search for the phrase “let it snow.” Provided your browser is up to the task — the latest versions of Chrome, IE, Safari and Firefox should all work — the search results page will begin to fill up with frost and snow.

Once the search results are sufficiently covered in white you can click and drag your mouse to write a message in the frost. And because nothing from Google is ever without a tie-in to Google+, just click the “+” button to share your Easter egg drawing with other Google+ users. To clear away the frost, click the “defrost” button.

Google is well known for its Easter eggs, the search results page recently did a flip for the phrase “do a barrel roll” and the company has even gone so far as to embed an entire flight simulator in Google Earth. If you’d like to see some other Google search Easter eggs, try typing “tilt“, “ascii art” (check out the Google logo) and our personal favorite, the quite subtle “recursion.”

File Under: CSS

Dabblet: An Interactive CSS ‘Playground’ in Your Browser

Dabblet: Live CSS editing (even better with monkeys)

CSS guru Lea Verou has unveiled a new project, Dabblet, which she describes as “an interactive CSS playground.”

Inspired by online editors like JSFiddle, Dabblet is an interactive testing app for CSS — write some code and instantly see the results in the same window. The site works in most modern web browsers, including Chrome, Firefox and Safari (Opera support is in the works).

Unlike JSFiddle where the emphasis is clearly on JavaScript, Verou’s app is designed from the ground up to focus on CSS. Among Dabblet’s nice features are automatic vendor prefixing for CSS 3 properties (via Verou’s -prefix-free library). The prefix-free script means you can just write, for example, border-radius instead of -moz-border-radius, -webkit-border-radius, -o-border-radius and so on.

Perhaps the most useful feature though is that Dabblet can save all of your work as GitHub gists. Not only those that making sharing your work with others easier it also ensure that even if Dabblet doesn’t last forever you’ll still have your data on GitHub.

The Dabblet source code is available on GitHub if you’d like to contribute or fork it for you own project (it’s licensed under the NPOSL 3.0 which carries a non-profit restriction).

Dabblet is simple to use, just dive in and start writing some code. However, not all of the advanced features are immediately obvious so if you’d like to see a kind of guide to Dabblet, head over to Verou’s blog where she has a basic screencast that shows Dabblet in action.

File Under: Browsers

Microsoft’s New Automatic Update Plan Could Mean the End of IE 6

Microsoft has announced that starting in January 2012 Internet Explorer will, like Chrome, Firefox and Opera, no longer pester you with update notices. Instead Internet Explorer will automatically download and install updates in the background.

The new auto-update feature will only apply to users who’ve opted into the automatic updates through Windows Update. Those that have opted in will be upgraded to the latest version of IE available for their system. If you’re still on Windows XP that means you’ll be updated to IE 8. Vista and Windows 7 users will move to IE 9. The Windows Blog notes that when upgrading, your home page, search provider, and default browser settings will not be affected.

Internet Explorer updates have been offered through Windows Update previously, but unlike other “important” Windows updates, users needed to initiate the actual installation of IE updates via a dialog box. The only real change for most users in today’s announcement is that you’ll no longer need to mess with all those notification windows and dialogs. Instead IE will just seamlessly upgrade.

If you don’t want automatic updates, you can turn off Windows Update (though you should be aware that doing so could leave you with a insecure browser and operating system). Enterprise customers can opt out of the new auto-update mechanism using the IE 8 and IE 9 Automatic Update Blocker toolkits available from Microsoft.

The new auto-updating will ensure that users have the latest, most secure and stable version of IE, and web developers may be able to enjoy a fringe benefit as well — fewer IE 6 and IE 7 users on the web.

According to Microsoft IE 6 usage is currently at 8.4 percent worldwide, with some countries already under 1 percent while others, like China, remain high at 27.9 percent.

Microsoft has previously launched a campaign to kill off IE 6 and many large websites — like Google and WordPress — have already dropped support for the aging browser.

Web developers still supporting IE 6 may not need to do so much longer if Microsoft’s auto-update strategy pays off. Since the new auto-update mechanism will apply to IE 7 as well, it too may not need to be supported much longer. Of course, even in the best case scenario where IE 6 and 7 users drop below 5 percent worldwide, web developers would still need to contend with IE 8. While IE 8 was a huge step up from its predecessors, it still lacks support for most of the HTML5 and CSS 3 features found in modern web browsers.

Microsoft’s move to silent, automatic updates for Internet Explorer means that Apple’s Safari web browser is now the only browser that doesn’t default to automatically updating. Microsoft says that the auto-updating will roll out regionally, starting in January with users in Australia and Brazil and “scaling up over time.”

File Under: HTML5, Web Basics

Enough With the Apps Already

I never know if one of my blog posts is going to take off. Most don’t. But yesterday’s post about apps not being the future probably set some kind of record. It got a lot of links and a lot of reads.

Had I known it was going to get so much attention I would have spelled out exactly what I meant by app. The question came up e-mailing with Brent Simmons who wrote a post about my post yesterday. I didn’t understand the confusion until I did a little back and forth with him.

I said this: “I mean app as in ‘there’s an app for that.’”

I’m talking about the newspaper or magazine that, when you click on a link to go to one of their articles, puts up an interstitial telling you that you could read the article in their app instead. Initially, I installed one or two of these. The other day I installed a big comprehensive one from Google. Flipboard is the original one of these reading environments that is not the web. The New York Times has a slow, buggy, huge app for reading their news.

Now don’t get me wrong; there’s no reason they shouldn’t produce these apps. Go ahead. They have every right. But I also have every right not to use them. And if they insist, as the New York Post does (its content isn’t available for iPad users on any other terms) I can just skip their content altogether (which in the case of the Post, who gives away their paper at subway entrances in NYC and is an awful Murdoch trash rag that would be an insult to dead fish to be wrapped in it, feels just right).

If that’s all there was to it, I probably never would have written this piece. But last week I read about a speech given at LeWeb in Paris by George Colony of Forrester Research, that got a lot of coverage. He said the web is over, and apps are the future. (BTW, when you search for George Colony on Google they’re so sure you meant George Clooney they don’t even offer the choice of George Colony.)

It was that speech, plus Google’s app, plus a well-timed interstitial that got me thinking: Why is it that I find this concept of the future so repulsive?

I wrote five pieces yesterday. I guess that was the best one. Sure hit a nerve. A lot of people agree. Enough with the apps already.

I think the publishers like the idea because it offers hope of a new paywall, an electronic one. My guess is that it’s a hope in vain.

Tablets are almost ideal reading environments. I don’t think, as some developers do, that the iPad is the ultimate. I think it’s heavy and cold, and makes my arm fall asleep when I read lying down. I think the software is a glitchy. Like great movies, great computer experiences are all about suspension of disbelief. If I forget I’m reading on an iPad and get consumed by the story, then the technology is working perfectly. The iPad experience is good, but there’s still a way to go. And all this business about apps is a real spoiler for suspension of disbelief. I’m clicking a link, expecting to learn more about what I was reading (that was certainly the author’s intent) but instead I get an ad for an app. If I seriously consider it, I’ve lost my train of thought. If I actually take the detour and install it, I’ve lost big time. The best way to minimize the loss is hit the Back button and skip it. But that’s a loss too. I clicked the link for a reason. And that was thwarted.

I’d be happy with a pref that says to all websites “I’m never going to install your app, so please don’t bother with the pitch.” Sort of like a No Solicitors sign on the front door of my house (which I don’t have; it’s too rude to people who are not solicitors).

BTW, I wrote a piece a month ago about Google’s search website on the iPad and how awful it is. They made it even worse. Now if you click on the Classic link at the bottom of the page you lose your search string and have to enter it again. At least in the past when you clicked Classic, after scrolling to the bottom of the page, you got the search results you were looking at in a more compact form.

To anyone from Microsoft who may be reading this far, here’s a chance to get a bunch of iPad users. Make Bing work exactly like Google on the desktop, on the iPad. Or offer it as an option. I will use your search engine from now on on the iPad if you do that. Google is deliberately screwing their iPad users. Now you guys can be the heroes.

All of this is of course IMHO, as if that needs to be said. But when there are a bunch of new Apple zealots reading stuff here calling me “some people” or “this guy” in my own blog, well it needs to be said.

Also, I let comments run more or less rampant in the last post. It got to be too much to moderate them all. Even so, if a comment required my approval and it was idiotic or unnecessary (How many times do we need to hear that there are things called intents?) I just let it sit there unapproved. You don’t have a right to place your ideas here. If I’m not reading your book-length comment, why should I impose it on my readers?

This post first appeared on Scripting News.

Dave Winer, a visiting scholar at NYU’s Arthur L. Carter Journalism Institute, pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software. A former contributing editor at Wired Magazine, Dave won the Wired Tech Renegade award in 2001.
Follow @davewiner on Twitter.
File Under: Blog Publishing

New WordPress 3.3: Less Flash, More Responsive Design

WordPress has released version 3.3. Dubbed “Sonny” after jazz saxophonist Sonny Stitt, WordPress 3.3 packs in a number of worthwhile upgrades, including a new responsive design that adapts the WordPress admin to smaller screens.

To get the latest version head over to the WordPress downloads page. If you’re already using WordPress you can update from the WordPress dashboard (naturally we suggest backing up your files and database before you upgrade).

Among the changes that make WordPress 3.3 well worth the upgrade is the new responsive admin design. While there are mobile apps from managing your WordPress site on the go, the actual web admin has never adapted to small screens. That changes with WordPress 3.3 and its new responsive admin page, which reflows content to fit the screen you’re using.

Responsive design — that is, using liquid layouts and scaling media to fit any screen size — is moving into the mainstream in a hurry. The past year has seen several high-profile websites relaunched with responsive designs, but WordPress 3.3 is likely the most widely used site yet to embrace responsive design.

Other changes in WordPress 3.3 include a slicker sidebar with “flyout” submenus which put everything in the admin site just a single click away. There’s also a new drag-and-drop uploader, which means you can drag and drop images from your desktop right into the media upload box in the admin (provided you’re using a browser that supports HTML5′s drag-and-drop API). Behind the scenes WordPress is using Plupload to handle the drag-and-drop features. In browsers that support it Plupload will use HTML5; for older browsers it falls back to Flash.

Anyone working on a site with numerous writers and editors will be happy to know that this release features much improved co-editing support. If you’ve ever seen messages like “Warning: [username] is currently editing this post,” you’ll be happy to know that it will now only appear when someone is actively editing a post. Previously the message would often appear even if your co-writer simply left the window or tab open in their browser.

For a complete list of changes and new features in WordPress 3.3, see the release notes.