Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

dendiz

macrumors newbie
Original poster
Aug 21, 2008
3
0
Is there a plugin for safari that would make the address bar act like the awesomeBar in firefox 3, where i can just type a few keywords and all the matching URLs from my browsing history are displayed?
 
i do have safari 3.1.2 but this doesn't work like FF3. For example, lets say i visited this url, and it's in my browsing history:
http://www.myurl.com/mypath/
when i type "myurl mypath" in FF3 this url appears in the dropdown, but in safari in doesn't
 
i do have safari 3.1.2 but this doesn't work like FF3. For example, lets say i visited this url, and it's in my browsing history:
http://www.myurl.com/mypath/
when i type "myurl mypath" in FF3 this url appears in the dropdown, but in safari in doesn't

My Safari does exactly that.

I type 'mac' and get a list based on my history and bookmarks.
 

Attachments

  • Picture 1.png
    Picture 1.png
    78.9 KB · Views: 245
My Safari does exactly that.

I type 'mac' and get a list based on my history and bookmarks.

thats not "exactly", is it?

try type more than one word in safari's urlbar and see what you get from it.

awesomebar isn't awesome just because it has history and bookmark as database. Its awesome because how it makes getting where users want easier, by its operational functions.
 
I agree, I have tried all of the above add-ons and there is nothing that makes Safari 4 work quite as 'awesome' as Firefox's AwesomeBar.

E.g. if I visited an Apple Store page a week ago called "MacBook Pro", I could type into Firefox "mac" or "pro" and it'd come up in the address bar almost telepathically. In Safari I'd be lucky if it came in when I typed "store" as Safari only looks at the beginning of the website URL (store.apple.com) or Title, not in the middle or elsewhere. So even if I typed "Apple", that site wouldn't come up as neither the URL or Title begin with 'Apple'.

Furthermore AwesomeBar learns, so once I have typed in "mac" it will in future put the site at the top of the results because it knows I like to type that then click the resulting suggestion.

This is extremely useful when you can only remember part of a website name, and has actually resulted in my hardly ever using the bookmarks menu - I used to have to navigate through all the sub-menus of my 100s of bookmarks, but with Firefox I can just type a few letters of what I want, and there it is! It's magic, and until Safari supports something identical, I imagine it will be a deal-breaker for many people.
 
E.g. if I visited a site a week ago called Apple Support Discussions, I could type into Firefox "dis" and it'd come up in the address bar almost telepathically. In Safari I'd be lucky if it came in when I typed "Apple" as Safari only looks at the beginning of the website URL or Title, not in the middle or elsewhere.
Your point is valid but you use kind of a bad example, since the URL for the Apple Support Discussions is discussions.apple.com so it will come up. Perhaps using "supp" makes a stronger case.
 
Okay I have edited my post to be more accurate for your Royal Pedanticness ;) The new example is quite shocking I think - it can't even find an Apple website when I type "Apple".
 
You realize that WebKit (the code that powers at least 95% of Safari) is an open source project, right?

You can submit a bug report directly to http://webkit.org, maybe even submit a patch if you know how.
 
Trying inquisitor

I think the major fail with safari is the way its setup. everything has a place and there is a place for everything.

Prime example being the address bar not forwarding you to a search site when it is unable to connect to an invalid url like say "mac rumors" instead of "macrumors.com".

however using the google bar with an addon like inquisitor (one of many which is broken in safari 64bit) is much closer to the suggestions we would like to get in the primary address bar.

Also funny side note I tried to install Inquisitor in safari 64bit (Snow Leopard edition) I found that not only does the plugin not work but the page also did not render properly in safari LULZ
 

Attachments

  • Screen shot 2009-09-08 at 8.30.56 AM.png
    Screen shot 2009-09-08 at 8.30.56 AM.png
    219.5 KB · Views: 80
download safari 4? and it does this with no plugins needed. and you get the cool top sites page in you bookmarks bar, as well as a few other enhanced features. I downloaded it long before I upgraded to SL.. no problems, love it:D
 
download safari 4? and it does this with no plugins needed. and you get the cool top sites page in you bookmarks bar, as well as a few other enhanced features. I downloaded it long before I upgraded to SL.. no problems, love it:D

You guys are misunderstanding what the Awesome bar is. For example, if I want to come back to this thread next week in Firefox, I can hit Cmd-L to get to the location bar, and type "Awesome bar safari" and come directly to this page. You don't need to know any part of the URL as you can use titles as well.

It is far different from the way Safari handles it. If Safari ever implemented a similar feature I would move to using it in a heartbeat.
 
You realize that WebKit (the code that powers at least 95% of Safari) is an open source project, right?

You can submit a bug report directly to http://webkit.org, maybe even submit a patch if you know how.
Webkit is the renderengine that Safari uses. Safari itself is a bit more than just webkit so submitting a bug to webkit for resolving a Safari interface issue will most likely be closed instantly. It's not something in webkit's control.

My Safari does exactly that.

I type 'mac' and get a list based on my history and bookmarks.
Safari 4 and Firefox 3 & 3.5 have both something similar regarding the addressbar. They both are able to search through the history and bookmarks to dig up a site. And that's where the similarities end. In Safari you can only dig up a site if you type in the first letters of its URL, which means you actually have to remember the first part of the URL. Firefox is much better at digging up sites because it can do what Safari does plus it can use keywords (anywhere in the URL or title of the page), tags and the keyword field. From a user perspective Firefox is an awful lot better at finding a site you forgot. This functionality is all about being able to find the sites you forgot and that is not accomplished with Safari's way of doing it since you need to remember the url. Firefox does not require that, the only thing you need to do is remember *something* about the site. That is a more natural way of doing things. If the list of results is to big you just specify some more keywords to narrow it down.

Try it for yourself. A default Safari 4 will have a bookmark for google.com and one for maps.google.com. Type in "maps" and the only result will be maps.google.com. Type in "google" and you'll get google.com as the only result. You can also try youtube: type "tube" and it won't find youtube.com but it will if you type "you". Do the same thing in Firefox and it will always return anything that has that keyword in it. So searching for "google" will return google.com and maps.google.com; searching for "tube" or "you" will return youtube.com. And so on.
 
Webkit is the renderengine that Safari uses. Safari itself is a bit more than just webkit so submitting a bug to webkit for resolving a Safari interface issue will most likely be closed instantly. It's not something in webkit's control.

It's not very wise to make assumptions about how projects work when you, in reality, clearly have little knowledge about how the project actually works.

In addition to being a rendering engine, WebKit is the UI for Safari. If you took 3 seconds to visit http://webkit.org and download a nightly you would find that the app you've just downloaded is in every way equivalent (all the way down to the preference pane) to Safari except for the icon (it's a little more golden to differentiate WebKit builds from official Safari releases). The only real difference is the name and possibly a little extra (1%) fairy dust that goes into each release-- all of which eventually get backported. This includes all of the code for OSX and the Windows releases too. It is all open sourced.

Opening a UI related ticket at WebKit would be accepted, and in fact it's quite common, since, as I said, the WebKit guys implement the UI that you will eventually see in the Safari release.

Next time, rather than assuming you know how open source projects work, you should do a little research.
 
It's not very wise to make assumptions about how projects work when you, in reality, clearly have little knowledge about how the project actually works.
Then why on Earth are you still commenting?

In addition to being a rendering engine, WebKit is the UI for Safari. If you took 3 seconds to visit http://webkit.org and download a nightly you would find that the app you've just downloaded is in every way equivalent (all the way down to the preference pane) to Safari except for the icon (it's a little more golden to differentiate WebKit builds from official Safari releases). The only real difference is the name and possibly a little extra (1%) fairy dust that goes into each release-- all of which eventually get backported. This includes all of the code for OSX and the Windows releases too. It is all open sourced.
That would be due to the fact the webkit you downloaded uses the Safari GUI. That's why it looks and acts like Safari does. The only GUI thing they develop is the WebInspector.

Opening a UI related ticket at WebKit would be accepted, and in fact it's quite common, since, as I said, the WebKit guys implement the UI that you will eventually see in the Safari release.

Next time, rather than assuming you know how open source projects work, you should do a little research.
Yes please, do some research next time like reading the website which you quite obviously didn't do. The frontpage says:

WebKit is an open source web browser engine. WebKit is also the name of the Mac OS X system framework version of the engine that's used by Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML and JavaScript code began as a branch of the KHTML and KJS libraries from KDE. This website is also the home of S60's S60 WebKit development.

One of their non-goals:
WebKit is an engine, not a browser.
We do not plan to develop or host a full-featured web browser based on WebKit. Others are welcome to do so, of course.

And how you should run your freshly build Webkit:
Running WebKit

1.

Type this command to run Safari with the WebKit you built:

WebKit/WebKitTools/Scripts/run-safari

Use the --debug option for a debug build:

WebKit/WebKitTools/Scripts/run-safari --debug
In fact running Webkit on Windows requires Safari, without Safari you can't run Webkit. Which is quite obvious for something that is a render engine and not a webbrowser (as they say themselves).

It might be that the same guys that work on Webkit also work on Safari but that really does not mean they are the exact same projects or that Webkit has a GUI.


So next time read the website you're linking to before ranting on someone else because as you can see it will backfire ;)

BTW: I am running the Webkit nightlies for a couple of years now and know what they are and what they do (and how you can disable the standard homepage it starts with). I've also tried using it on Windows which is quite some work compared to drag 'n dropping Webkit to /Applications.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.