Could they not turn the development over to the community? Put the source code up on Github? Seems a shame to kill it off. *I'm not a user and not sure how popular the browser is.
Camino browser reaches its end
71–80 of 127 posts
Re: Camino browser reaches its end
#72Earlier quoted context omitted.
did it look like this [1]? that's the UX nightly available at [2]. it's a new theme they're working on, but it's got a few versions to go before it makes it into stable. i'm loving it, but they're removing/changing a couple of customization features so people are freaking out. we'll see what the final product ends up looking like. [1] http://i.imgur.com/Gfns2MS.png [2] http://people.mozilla.org/~jwein/ux-nightly/
That's hardly a good Mac UI. On the Mac: 1. Tab close buttons should be on the left, not the right. 2. They got the tab title right, in the center, but site icon should be right next to the site title, not on the far left.
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.
Re: Camino browser reaches its end
#73One feature Camino ha and that I really miss in other browsers is that it displayed whether files in its download window were still there. That sounds rather trivial, but made it a perfect "file inbox", where I could quickly see whether I still needed to review/move a file.
And the fact that it was more in sync with the OS X desktop experience than Firefox (back in the days; got better) and Safari (brushed metal)...
Of course nowadays, a hierarchical tab sidebar is my one "exclusive" killer feature, and as of yet only Firefox has that (via add-ons).
Re: Camino browser reaches its end
#74Re: Camino browser reaches its end
#75Earlier quoted context omitted.
That's hardly a good Mac UI. On the Mac: 1. Tab close buttons should be on the left, not the right. 2. They got the tab title right, in the center, but site icon should be right next to the site title, not on the far left.
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.
Re: Camino browser reaches its end
#76Earlier 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…
did it look like this [1]? that's the UX nightly available at [2]. it's a new theme they're working on, but it's got a few versions to go before it makes it into stable. i'm loving it, but they're removing/changing a couple of customization features so people are freaking out. we'll see what the final product ends up looking like. [1] http://i.imgur.com/Gfns2MS.png [2] http://people.mozilla.org/~jwein/ux-nightly/
Yes! Thank you. While I don't think it looks or feels perfect yet, it at least shows that FF is still in the game working on things like this.
Re: Camino browser reaches its end
#77Earlier quoted context omitted.
did it look like this [1]? that's the UX nightly available at [2]. it's a new theme they're working on, but it's got a few versions to go before it makes it into stable. i'm loving it, but they're removing/changing a couple of customization features so people are freaking out. we'll see what the final product ends up looking like. [1] http://i.imgur.com/Gfns2MS.png [2] http://people.mozilla.org/~jwein/ux-nightly/
That's hardly a good Mac UI. On the Mac: 1. Tab close buttons should be on the left, not the right. 2. They got the tab title right, in the center, but site icon should be right next to the site title, not on the far left.
I think the reason they have the icon/close button switched is because when you pin a tab it goes on the left side of the screen.
Re: Camino browser reaches its end
#78“Camino is not receiving security updates” “Camino reaches its end” “Camino is no longer being developed” I don’t like the tone of this press release. They make it seem like they’re not responsible for the lack of updates and that Camino died a natural death. They didn’t offer an explanation nor did they give any advance notice. Not very classy.
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
Re: Camino browser reaches its end
#79Could they not turn the development over to the community? Put the source code up on Github? Seems a shame to kill it off. *I'm not a user and not sure how popular the browser is.
Camino has been open source and developed entirely by a community of volunteers for most of its life. There were extensive instructions on getting involved on the website for many years. There was even a specific push to recruit new people a year ago to make the transition to WebKit so that it could continue to use a modern engine, which is the only way it could have survived once Gecko stopped supporting embedding.
If there were a community of people with the time/interest/skill to develop it further, the project wouldn't have shut down in the first place.
Re: Camino browser reaches its end
#80Earlier 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). You can do that using a custom key binding in ~/Library/KeyBindings. Firefox ignores this and still insists on home/end working on the full document. But even worse: in the new G…
>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.