All posts tagged ‘safari’

File Under: Software & Tools

Inquisitor Search Plugin Incorporates BOSS

Inquisitor 3.2A new version of the Inquisitor plugin for Safari has been released, and it uses Yahoo’s Build Your Own Search Service (BOSS).

Like a lot of Safari, Inquisitor is fast, even though it uses search suggestions and shows some results inline. Also like Safari, Inquisitor is pretty. The overlay is a handsome black and each result has the favicon of its site next to it.

The number of search suggestions and results are configurable. Check out “Search” in the Safari preferences to find the Inquisitor settings. The plugin also lets you switch away from using Yahoo search.

The configurable search engine is notable because Yahoo owns Inquisitor. The web granddaddy bought the plugin in May for its search interface innovation and to support Mac-specific initiatives.

It is refreshing to see a big company let a product remain somewhat independent. Yahoo offered the upsides (improved search performance according to Inquisitor creator David Watanabe), but now is staying out of the way.

Aside from ID switchover debacles, Yahoo has kept its acquisitions independent. Flickr still looks like Flickr. Delicious looks like Delicious. And Upcoming, despite recent UI tweaks and moving to a Yahoo sub-domain, maintains a non-Yahoo appearance.

[via SearchEngineWatch]

See also:

File Under: Mobile, Software & Tools

Torch Fires up Webkit-Powered Windows Mobile Browser

Torch Mobile’s Iris browser takes the power of the Webkit rendering engine to Windows Mobile devices. The mobile browser was released Tuesday.

The browser itself is not unlike the many iPhone Safari clones popping up around the mobile web since iPhones first hit the streets. You load up a page, the page appears as a mile-high overview, you double click in an area and it zooms in, you scroll the page with your finger. In fact, it has a lot in common with another full-fledged browser on Windows Mobile, Opera Mobile 9.5.

The significance of the Iris browser derives from how the page is rendered. In Iris’ case, the page is rendered using Webkit, the same powerful rendering engine behind Safari. Webkit is robust, fast and quick to jump on the newest and coolest web standards. It’s also an open source project, which means, thanks to Iris, Windows Mobile users won’t have to wait for Safari to be ported from the iPhone to Windows Mobile for the same web surfing experience.

Other features of the Iris browser include:

  • Multiple Windows and Tabs
  • Netscape plug-in API
  • HTML 4, JavaScript, CSS, bookmarks, cookies and cache (like we said, it’s fully powered browser)
  • Support for input devices and mobile hardware features such as touch screens, keyboards and rotatable screens

The browser playing field on Windows Mobile is a sparse one. Iris has entered the ring to compete with Opera for best Windows Mobile Browser. Opera is even more strict than Webkit when it comes to web standards, is also a fully operable browser and touts some pretty fast speeds too. Also available for Windows devices is Skyfire, which delivers image snapshots of web pages instead of rendering the page on the device itself.

Finally, there is the first generation browser packaged with Windows Mobile: Internet Explorer. It’s clumsy and manipulates pages to fit and render on it. It’s anything but the full-powered browser Safari, Opera and Torch is.

Download the Iris browser at the Torch Mobile website.

See Also:

WebKit Experiments with CSS Variables

WebKit, the code that makes up the guts of browsers such as Apple’s Safari, has gained a much-requested new feature with the addition of variables in cascading stylesheets.

The feature, which won’t be available publicly until the next major release of Safari — and then only if it survives this experiment — is available now with its latest nightly WebKit build.

The enhancement comes after ten years of pleas for the feature by web developers. It would make designing and reading website code much easier by allowing developers to reference commonly-used styles by names chosen by the site’s designer. For example, watch how variables make this little piece of code, used to make the background of the page and tables light gray, a little more readable:

Without variables:


//Sets the background of the page and tables to the hex code for the color gray.

body {

   background-color:#ECEAE1;}

table {

   background-color: #ECEAE1;}

With CSS variables:


//Defines "DefaultBGColor" to light gray

@variables {

  DefaultBGColor: #ECEAE1;}

//Sets the background and any table on the page to the default background color

body {

  background-color: var(DefaultBGColor);}

table {

  background-color: var(DefaultBGColor);}

Current implementations of CSS have some standard variables for properties like alignment or color (“left,” “dark blue” or “red,” for example). However, unless you design your site around those pre-defined colors, you’re stuck having to memorize hex codes and pixel lengths. This is especially challenging for sites with multiple designers referencing the same code. Variables would mirror other coding standards by making these references configurable and recognizable according to site design.

Webkit, the rendering engine that powers Apple’s Safari and Linux’s Konqueror, is the first browser to support CSS variables. Web designers are not likely to take advantage of it until other major browsers, like Microsoft’s Internet Explorer and Mozilla’s Firefox, hop on the bandwagon. Still, it’s a nifty advancement, and something worth noting for the future.

To get started with Cascading Style Sheets (CSS), follow Webmonkey’s tutorial.

File Under: Software & Tools

Safari 4 Preview Offers Easy Single-Page Desktop Apps

webkiticon.jpgNot to be outdone by the release of Opera 9.5 and Firefox 3, Apple has given developers a sneak peek at the next version of its Safari web browser. Safari 4 will offer the ability to save a webpage as an application and adds new options for window and tab behavior.

Safari 4 is also the first version to pass the ACID 3 browser rendering test and is reportedly much faster than its predecessors (partially due to the new JavaScript rendering engine we looked at earlier).

The ability to save a webpage as a standalone app pretty much mimics Mozilla’s Prism application and eliminates the need for third-party apps like Fluid (though if you want that feature today, Fluid is a good way to get it).

Safari 4 also introduces a new preference to specify whether new tabs or windows open with your homepage, the same page, empty page or bookmarks.

There are some other small changes as well, but primarily under-the-hood stuff in WebKit, the engine that powers Safari. So far Apple hasn’t hinted at a timeline for Safari 4, but we’ll be sure to keep you posted.

[via World of Apple]

See Also:

File Under: Software & Tools

SquirrelFish JavaScript Upgrade Gives Safari a Huge Speed Boost

SquirrelFishApple’s annual developer conference won’t kick off until June 9 but already there’s some exciting news for Mac fans. The team behind Apple’s Safari web browser have announced a new, and much faster, JavaScript interpreter for WebKit, the engine behind Safari.

WebKit’s previous JavaScript handler was no slouch, but the new engine, dubbed SquirrelFish, is up to 1.6 times faster in standard JavaScript speed tests.

That’s good news for iPhone users since SquirrelFish will no doubt make its way into Mobile Safari at some point. The speed boast in Mobile Safari should mean your favorite JavaScript-heavy apps — like Gmail and others — will run faster once SquirrelFish is added.

For now the new JavaScript engine is limited to nightly builds of desktop Safari, but once it’s stable look for a Safari update with the new features.

If you’d like more info on why SquirrelFish is fast, head over to the Surfin’ Safari blog where developer Geoffrey Garen explains the details:

SquirrelFish’s bytecode engine elegantly eliminates almost all of the overhead of a tree-walking interpreter. First, a bytecode stream exactly describes the operations needed to execute a program. Compiling to bytecode implicitly strips away irrelevant grammatical structure. Second, a bytecode dispatch is a single direct memory read, followed by a single indirect branch. Therefore, executing a bytecode instruction is much faster than visiting a syntax tree node. Third, with the syntax tree gone, the interpreter no longer needs to propagate execution state between syntax tree nodes.

Safari nightly builds can be downloaded from the WebKit site.

Or you could just wait for the SquirrelFish engine to hit Safari and spend the interim pondering the super cool logo of a somewhat drunken-looking SquirrelFish.

[via Reddit]

See Also: