Google Chrome Coming Tomorrow

Posted on September 1st, 2008 | No Comments »

Over at the Official Google Blog, Google announced today that they are releasing “a fresh take on the browser” tomorrow which they have dubbed Google Chrome.  Here are the choice tidbits from the article (at least from my perspective):

  • The release will be a beta version and will be released in more than 100 countries.
  • Google “started from scratch” and used the “best elements out there.”
  • The browser is apparently clean and fast.
  • The browser supports tabs, and each tab is isolated in such a way that a crash in one shouldn’t affect the others.
  • Google created a new JavaScript engine for the browser, which they call “V8.”
  • Google is working on versions for Mac and Linux, but it doesn’t sound like they will be ready to download tomorrow.
  • The browser is based off of both WebKit and Firefox, and will be released as open source, just like they are.

There are a few other details already available on Wikipedia:

  • The address bar will have auto-completion features (apparently called “omnibox”).
  • Web apps can be launched in their own web browser window with very little surrounding chrome.
  • It is integrated with Google Gears.

Be sure to drop by the Official Google Blog tomorrow if you feel like giving the beta a test drive.  Not that I really needed to tell you that, since I’m sure every single browserphile running Windows will be downloading it tomorrow and seeing what it’s all about.

Tags: , , , , , , , ,

Testing WebKit Nightlies on Windows

Posted on July 8th, 2008 | 2 Comments »

Anyone who has followed the support for web standards in today’s popular web browsers knows that the WebKit rendering engine has been at the forefront of that support.  Therefore, if you’re a browserphile like me, there’s a good chance you’re interested in testing out the latest and greatest WebKit build so you can see what all the fuss is about.  The following is a step-by-step list of things I had to do to get WebKit nightly builds working on my Windows computer.

  1. Download and install the Safari web browser for Windows.
  2. Download the latest WebKit nightly build for Windows.
  3. Unzip the contents of the download to a location like C:\Program Files\WebKit Nightlies.
  4. In the contents of the extracted folder, run (either from the command line or by double-clicking on the file) run-nightly-webkit.cmd.
  5. Watch as several necessary files are copied over to your Safari installation directory.
  6. If Safari launches and then crashes, fear not.  First try running the run-nightly-webkit.cmd file again.  If the crashing persists, work backward through the Windows Nightly Build Archive until you find a working build.  Remember, nightly builds are almost always considered dangerous (which is why the Firefox nightlies are called “Minefield“) so it may take some tinkering around before you find a good one.  The last good one I found at the time of writing was r34388.
  7. If Safari launches and renders the default start page, you’re in business.

If you want to verify that you’re indeed using the WebKit nightly build you downloaded and not the default Safari rendering engine included with the latest version (3.1.2 at the time of writing), an easy way to check is to head on over to the Acid3 test.

This is what the test looks like in Safari 3.1.2:

Screenshot of Acid3 in Safari 3.1.2

And here is what it looks like in WebKit nightly build r34388:

Screenshot of Acid3 Test in WebKit Nightly Build r34388

Pretty cool!

I’d be remiss not to mention Swapnonil Mukherjee’s previous post on the subject, which proved to be a pretty good guide to getting a WebKit nightly build running on my computer.

Tags: , , , , , , , , , , , ,

Twitter Watch #2

Posted on May 15th, 2008 | No Comments »

Last time around I used Tweet Scan, this time I’m giving Summize a try:

Tags: , , , , , , , , , , ,

Around the Browsersphere #10

Posted on May 11th, 2008 | 5 Comments »

There are some rumblings in the browsersphere as of late with a Firefox 3 RC1 release right around the corner, news that the latest service pack for XP isn’t compatible with a pre-installed IE8 Beta 1, etc.  So let’s get caught up.

General

Avant

Firefox

Flock

Internet Explorer

Konqueror

Maxthon

Opera

Opera Mini

Safari

Minor Players

Web Standards

Holy cow.  That’s a lot of information.  The browsersphere is a bustling place.  Hopefully you found something useful in all that.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Around the Browsersphere #9

Posted on April 28th, 2008 | No Comments »

Last time around, I didn’t get any feedback on the format of these “Around the Browsersphere” posts, so I’ll give a slightly more organized approach a try and we’ll see how it goes.

Camino

  • Camino 1.6, which features a customizable toolbar search field, software update capabilities, a scrolling tab bar, etc., was released on the 17th.

Firefox

Flock

Internet Explorer

Konqueror

Maxthon

Mozilla

Opera and Opera Mini

Safari

SeaMonkey

Minor Players

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

Digg Watch #3

Posted on April 20th, 2008 | 2 Comments »

It’s been a few months since we caught up with the popular web browser-related submissions on Digg, so let’s do something about that:

Tags: , , , , , , , , , , , , , ,

Safari Closing in on Acid3

Posted on March 7th, 2008 | 2 Comments »

According to Dave Hyatt, the Safari team has made significant gains of late in achieving compliance with the new Acid3 test.  Apparently they’ve made the leap from scoring 39/100 on the test to 90/100 after addressing issues with CSS3 Selectors, general parsing bugs, SVG and DOM Level 2 features.  According to Hyatt, the remainder of the issues tend to fall into the SVG category, and since they are getting so close to Acid3 compliance, they will be updating Surfin’ Safari regularly with updates on their progress.

Tags: , , , ,

Latitude Q&A with Sebastiaan de With

Posted on March 6th, 2008 | 3 Comments »

As promised, I sent some questions to Sebastiaan de With, the icon and interface designer who came up with the idea for a new web browser, Latitude, which was covered here at Browsersphere recently.

Sebastiaan was kind enough to come back with very thorough and informative answers, so I’ve posted them here in full, with a few minor edits and links added.

Has the idea for Latitude been lingering in your mind for a long time, or is it something that sprang to life only recently?

I’ve been thinking about browser interfaces since the last few months, mostly inspired by the expressions of Mac users about the lack of a Mac-experience in browsers like Firefox and Flock. Although most people consider an .app bundle adequately ‘Mac-like’, I think it goes down to the very mental model the user has of the software he’s using. Take, for example, Safari’s bookmark management. There’s this great bookmark bar, that lets you toggle between the bookmark view and your website. It’s a tiny button that usually confuses some novice users I know, but I can understand that’s no priority. However, the same kind of view pops up if you access ‘History’ from the menu. It’s something a lot of users find confusing, because these completely different content views are all accessed from different places and are dismissed differently (discounting tabs and undo). Firefox also does this wrong, using a separate sidebar for anything you might be able to imagine. No user wants to think “in what sidebar is this thing I need?”

There [are] two options to improve on Firefox’s models; you either take away all the crud, without reinventing the basic principle (Safari’s path), or you re-think browser interfaces from scratch, keeping in mind the paradigms of Mac OS X, and for example iTunes. Why can my mother buy a song in iTunes, while she can’t find a fun movie on the internet, or keep track of what’s happening in the world?  It then struck me that original ideas should be implemented to reduce the screen estate the interface would consume, and the pieces of the puzzle soon clicked together. What do you want in a browser? I’m sure I could ask any intermediate computer user and get a list of his most wanted features. Now try condensing that into a new browser, with the basic premise that the UI should be minimal.

In your “My dream browser” post you wrote “I am aware of several ‘new generation’ browser projects, but none really line up with my ideas.”  Can you share a few of these “new generation” projects and/or why you think they fall short?

The two projects that really [caught] my attention were Flock and Shiira; these two browsers are ideologically opposed to each other. Flock tried to make an integrated browsing experience and failed, in my opinion. The Mac version of Flock once counted no more than 10 buttons; these days, its toolbar is chock full of nondescript buttons and widgets. To me, it wasn’t just visually busy, but it was mostly a browser that seemed like a big hassle to get my head around. I just want something I don’t have to learn, while still being feature-packed. Shiira really did much better in this regard, but simply went a different direction, reinventing parts of the interface, making things more intuitive and visual, but in no way expanding on the feature set of browsers. I really want both; an intuitive browser that’s as functional for viewing web content as the Finder is for viewing files on your disk. Finder doesn’t just handle one format of files either; it can handle your content. And in my opinion, that’s what a browser should do today. Focus on content.

The feedback to both of your posts on the subject has been very positive based on the comments.  Have you gotten a lot of other feedback through email or by other means, and has it been just as positive?  Are there any instances where you received constructive criticism or even negative feedback?

I’ve gotten a lot of email from developers and people who really want to see this developed. I chatted with a few developers, but as I’m very occupied as a full-time icon and interface designer, I can’t oversee or manage such a project right now.

I’ve gotten more than enough constructive criticism and even negative feedback; from people saying my interface mockups are just ‘someone with Photoshop‘ to dismissing certain ideas or even calling me names for proposing to take away the tab bar when the sidebar is active. I think a lot of people misinterpret my designs; most think it’s intended to completely throw every interface paradigm in browsers today overboard, but that’s the opposite of my intention.

I want to make a browser with a more accessible and less cluttered interface. For loose ideas, like the ‘Time Machine’ view for history I mocked up, criticism is fierce, while I’ve always mentioned that it is just a mock-up of a more visual way to view your history for one website, suggesting a different view for all website history. But most people who express the most intense critique fail to offer any real better solutions to the problem.

In your “Latitude” post, you wrote “Several developers have contacted me with the desire to develop it, and some have already actively begun programming whole aspects of it.”  Can you share what aspects have already gone under development?

Thanks to Apple’s WebKit, developers are able to implement a multitude of my interface ideas and gauge the feasibility other features I suggested . Currently, basic work is being done on making more intelligent sidebar behavior, fullscreen browsing, and changing things like Downloads and Bookmarks from their conventional format to something ready for the sidebar.

Will you be making the design document and centralized website you mentioned in that same post available for public consumption, or are you trying to limit it to only those actively working on the project?

I intend to make this as open as possible, and I hope all developers working on the project are eager to allow other people to chip in and collaborate to make a better browser reality.

I noticed some criticism of Firefox in your other blog entries.  Is this your primary web browser today?  If so, what do you think are its biggest shortcomings?

Although Firefox is not my primary web browser (Safari is), it is one of the most used browsers today, and the last beta version for OS X showed an interface that is absolutely nonstandard and horribly designed. I think Firefox, while aiming for a ‘good’ look and feel on all platforms, really fails to deliver on any, with perhaps the notable exception of Linux. As I said in the response to your first question, the lack of invention in the interface causes the user to go on a quest to find the features he needs, and disappoints most of the time in providing them.

Have you put any thought into working your visual design ideas into an already existing platform (e.g. Firefox) via extensions or themes in order to bypass all of the work that goes into creating a new rendering engine, etc.?

As I said in my response to question 4, WebKit already allows this, and thanks to that, I can deliver the interface in full Cocoa glory. Firefox (with the exception of Camino) still uses XUL to render its interface, which is something I wouldn’t want to touch with a ten foot cattle prod. Also, I think drastically changing the structure and interface of a browser like Firefox would require so much more than an extension, that working ‘from scratch’ is automatically the preferred option.

If readers of Browsersphere are interested in contributing, what kinds of help are you looking for?

Anything! If you can code a website, feel free to drop an email, but especially (talented) developers are encouraged to contact me to get details on the project before the official website goes live.

Tags: , , , , , , , , , ,

Around the Browsersphere #7

Posted on February 19th, 2008 | 1 Comment »

Believe it or not it’s been over three months since the last edition of Around the Browsersphere, so we’re long overdue.  Let’s get to it…

Tags: , , , , , , , , , , , , , , , ,

Digg Watch #2

Posted on January 16th, 2008 | 1 Comment »

As usual, web browsers are getting plenty of coverage over on Digg.  Let’s take a look at some of the hot topics over the past month.

Tags: , , , , , ,