Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Camino browser reaches its end

caminobrowser.org

Post reply on HN
Print view View original

91–100 of 127 posts

Re: Camino browser reaches its end

#91

Post by ams6110 »

Samuel_Michon wrote: post #81
gaius wrote: post #78

Earlier quoted context omitted.

From http://caminobrowser.org/blog/2011/#mozembedding As a purely community-based open source project, no one is employed to work on Camino; all Camino developers are volunteers, working on Camino in their spare time, as a labor of love. While maintaining embedding in a fork of Gecko is theoretically possible, we don’t have the manpower for a sustained effort of that kind

Ah, that explains a lot. It also shows the shadow side of open source software development: if the developers get bored, they can just up and leave. If all the devs do so, the project is dead but there’s no one there to call it. Users aren’t owed any explanation.

And this differs from commercial/closed source software how? Google Reader come to mind, as one example?

Re: Camino browser reaches its end

#92

Post by vvhn »

TazeTSchnitzel wrote: post #80
vvhn wrote: post #43

Earlier quoted context omitted.

>The one thing that drives me mad about Firefox on the Mac is it's Home/End behavior. Ever since migrating to the Mac, I have remapped the keys to work like on windows and Linux (operating on the current line instead of the current document) That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thin…

>That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thing Is it? I'm used to them going to the beginning and the end of lines on Linux.

The very next line you quoted tells you why that is the case on Linux now. if you used Linux in the late 90's, you will remember that a lot of the popular window managers/desktop environments aimed to make your transition from Windows 95 easier and the current Linux behaviour is a result of that.

Re: Camino browser reaches its end

#93

Post by Argorak »

UIZealot wrote: post #75
Argorak wrote: post #72

Earlier quoted context omitted.

Be aware that the UX alpha is highly unstable. Many things are not finished and from time to time just appear and vanish out of thin air. So it can only be used as a direction indicator and as such, I think it looks good.

Actually this tab style dates back to at least Firefox 3. I didn't check further back. It looks like XUL can't do it the right way, and they don't care enough to do it right.

It seems like sometimes the play with it and go back to the old one (which I actually like...).

BTW, the UX alpha is back to the old style.

Re: Camino browser reaches its end

#94

Post by vvhn »

pilif wrote: post #88
vvhn wrote: post #43

Earlier quoted context omitted.

>The one thing that drives me mad about Firefox on the Mac is it's Home/End behavior. Ever since migrating to the Mac, I have remapped the keys to work like on windows and Linux (operating on the current line instead of the current document) That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thin…

> You will find this behaviour in all Apple provided applications as well. not on my machine. As I said, I used ~/Library/KeyBindings/DefaultKeyBinding.dict to change it. If the OS provides a way to change defaults, I expect applications to respect that too - no matter the historical reasons. > >in the new Gmail compose window, not even Command-Left/Right works > cntrl-a and cntrl-e work. Yes, but Command-Left/Right…

If the application overrides the defaults (which is fairly common ), your changing the defaults does nothing (for that application and for the keys that might have been overridden). It sounds like Firefox overrides the defaults completely but in it's override "map" keeps some of the functionality the same as the default.

I havn't used it but this claims it will change the Firefox behaviour as well (specifically make them behave like windows for the home and end keys)

https://addons.mozilla.org/en-US/firefox/addon/keyfixer/

I think cmd-left and cmd-right are used by Firefox for " back" and "forward" so those never work on Firefox (unless perhaps you go find where Firefox specifies its key bindings and change them)

Re: Camino browser reaches its end

#96

Post by stuartmorgan »

ancarda wrote: post #45
eightyone wrote: post #5

Earlier quoted context omitted.

I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…

Since Camino is based off Firefox, is it possible to backport some of the OS X specific code? The primary reason why I'm still using Safari rather than Firefox is because it lacks Keychain support.

There have been two attempts that I know of (and probably more) to add keychain support to Firefox, once leveraging Camino’s code. The problem wasn't technical, but resistance from Firefox leadership to the idea. IIRC they were concerned about breaking the ability to move a profile folder from one OS to another.

Re: Camino browser reaches its end

#97

Post by as_if »

twic wrote: post #85
lttlrck wrote: post #82

Earlier quoted context omitted.

50+ tabs!!

I know! How does he manage to have so few?

he's one of the people who partly (because he's still over 10 tabs) gets the current bookmark-systems in browsers.

For most users the bookmarks seem to be broken/too complex. Never had the problem, maybe because I'm going crazy when I got over 10 tabs and want to get rid of them ASAP. :\

Re: Camino browser reaches its end

#98

Post by masklinn »

as_if wrote: post #97
twic wrote: post #85

Earlier quoted context omitted.

I know! How does he manage to have so few?

he's one of the people who partly (because he's still over 10 tabs) gets the current bookmark-systems in browsers. For most users the bookmarks seem to be broken/too complex. Never had the problem, maybe because I'm going crazy when I got over 10 tabs and want to get rid of them ASAP. :\

I have absolutely no idea what you're talking about. I don't use bookmarks, I used to put things in there and never find them when I needed them, so I've stopped doing that.

Re: Camino browser reaches its end

#99

Post by msujaws »

eightyone wrote: post #5
kunai wrote: post #2

I find this extremely saddening because Camino offered the best native experience for OS X, with all the polish of a well-designed Cocoa app, on top of Gecko. I'll miss Camino.

I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…

We're actually very far along in implementing what you saw in those screenshots.

You can download a Nightly build of it (that auto-updates) at http://people.mozilla.org/~jwein/ux-nightly/

Re: Camino browser reaches its end

#100

Post by jccalhoun »

redthrowaway wrote: post #38
wtallis wrote: post #36

I only stopped using Camino when I became dependent on some Firefox extensions (AdBlock, NoScript, eventually others). The big downside to Camino having a fully native UI was that it didn't have XUL support, so no cross-compatibility with FireFox extensions. As soon as one of the Mac-compatible WebKit browsers can replicate the functionality of AdBlock Plus, NoScript, and BetterPrivacy, I'll quit using FireFox on OS…

AdBlock Plus is available for Chrome and NotScripts replicates NoScript. I'm not sure what BetterPrivacy gets you that you can't do yourself by changing your cookie settings.

Notscripts hasn't been updated since December of 2010. ScriptSafe (used to be scriptno) is still being developed https://chrome.google.com/webstore/detail/scriptsafe/oiigbmn...

However, the author of noscript has said that it isn't technically possible to entirely replicate all of the features of noscript on chrome because extensions on chrome don't have the same kind of access as they do on firefox.

http://hackademix.net/2009/12/10/why-chrome-has-no-noscript/

Post reply on HN