It's very simple and there's no need to ask Apple's HIG. The developers decide what to put into the app and that's fine. That said, I'm not left with the impression that they carefully listen to what users request (no flames, it's just my humble opinion) and I also don't have the impression that there is something like a road map and a clear definition of what Camino 1.0 should look like. It's rather frustrating to read Nike's blog asking whether it wouldn't be best to just copy Firebird's UI... Stuff like this doesn't sound very optimistic.
From my perspective it seems clear that Safari is becoming what Camino once wanted to be, namely the browser for the masses with a limited feature set. OmniWeb will likely become the feature champion once it uses the Webcore engine and Firebird is already the feature champion for Mozilla (although it's the ugliest browser of them all). So where is the niche for Camino? I don't know, but I feel that the only way that Camino will get a significant user base is by embracing unique features that no other browser has or at least combinations of features that are special, e.g.:
- roaming access to bookmarks without .Mac
- Applescriptability (make a shared menu to access scripts and allow users to tap into EVERY aspect of Camino via AS). This would open up a lot of power user features for those who want it. Give us hooks for scripts to be executed on launch and quit, before and after accessing a URL, etc.
- Skins (I already posted an email, but Mike rather wants to copy Firebird instead of responding to my offer)
- Access all bookmark files from every browser installed in Camino
It's stuff like this that would make Camino unique and appealing. As it stands, I'm using Safari, not because it's better than camino, but simply because of my ability to synchronize bookmarks across Macs I use at home and at work.
-Reinhold
On Nov 18, 2003, at 3:34 PM, Josh Dady wrote:
On 11/18/03, Daniel J. Stern wrote:
Please note, this statement is NOT a quote of Apple's HIG or any other Apple document.
Right. In fact, that was my point. Two posts ago (I'm not continuing to quote this silly conversation), when you said that neither statement supports the idea of not having preferences to turn off type-ahead-find in the GUI, that same non-Apple statement was one of the only two statements I thought you could have been referring to.
Now, if you believe that my premise here (that S. Woodside's original
statement does not support the no-type-ahead-find-preferences policy),
then fine. I, on the other hand, entered hoping to maintain intelligent
discussion on an important topic (the proper balance of simplicity vs.
configurability) -- I no longer maintain this "optimistic appraisal of
the situation."
_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
