Google Bar: Any solution that requires "editing a text file" for added functionality is usually not the best solution. I suggest you take a look at firebird's approach. it's an extremely simple addition.
I'll take a look at fb's approach, but this is a slippery slope, akin to "what can just one more pref hurt?" For the people that want to customize it, a mechanism is provided. For people that do not, the UI isn't cluttered. I could be swayed, but it doesn't seem to be a feature that 95% of users are demanding and thus I don't believe it deserves UI. Perhaps a slightly richer default set might mitigate this issue?
I would have to agree - if we're trying to reach as broad an audience as possible, we should be trying to make it as easy and straight-forward as possible to add new search engines to Camino. This is one thing that we can trumpet over Safari, if an effective UI is created to handle this, as you already know that Safari is hardwired for Google.
I concur that there shouldn't be "pref-itis" ala Mozilla, but this is specifically something that should be easy and intuitive for users to gleam. The way that Omniweb handles this (and all of its prefs) is really beautiful, and useful. If you haven't looked at OW in a while, download a copy sometime.
Neil --- Slumming at the beatnikPad : http://www.beatnikpad.com/ Working at theNonsuch: http://reblog.thenonsuch.com/ e-mail: [EMAIL PROTECTED] | yeah.
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
