Slashdot Mirror
Mozilla Camino 1.0 Released
Mini-Geek writes "MozillaZine is reporting that Mozilla Camino 1.0 has been released. The latest release includes a new tab bar appearance, pause and resume for downloads, improved advertisement and popup blocking, enhanced certificate support, bundled java embedding plugin, form fill from Address Book and inline search of history and bookmarks. See the Camino 1.0 Release Notes for more details."
According to the site, it is a "Gecko based native Mac OS X browser." How is it different from Firefox?
The link in the story appears broken. Here's the actual ,a href="http://www.caminobrowser.org/releases/1.0.ph p">Camino 1.0 release notes
There are a couple gesture programs for OS X that you can use. FlyGesture is way cool, and from one of the best indie deveopers around, but at 24.95, it's a little pricey. CocoaGestures is free, but not quite as cool.
The nice thing about either of these is that you can use them with any browser.
there's more than one way to do me.
on OSX I've actually started using Safari more than FF - but maybe Camino will change that Just to make sure it's clear, Camino is not a build of Firefox. It is a separately managed project specifically designed for the Mac, but it uses the same rendering engine.
This message will self-destruct in 5, 4, 3...
Switching tabs using PowerBook keyboard is also a bit complicated, as one has to press option, and PowerBooks only have the left one, so two hands are needed. Safari has better shortcuts (cmd-shift instead of cmd-option) in this sense.
Using the "Keyboard Shortcuts" part of the Keyboard & Mouse System Preference, you can change Camino's "Previous Tab" and "Next Tab" commands to be whatever you want, including the Safari way.
I watched C-beams glitter in the dark near the Tannhauser gate.
At least on Mac OS X, Firefox has some very specific problems that can contribute to this perception.
Bug 141710: Holding down mouse button forces 100% CPU on Macs is a real stinger. It it seems from discussion on this bug and a number of others that the real solution is to move Firefox on OS X off of Carbon and onto the Cocoa framework (Bug 111230: Use Cocoa for Widget instead of Carbon. That effort has an independent dev working on a port, but there seems to be little official impetus to make OS X into a first-class platform for Firefox. In response to the obvious cries of "go write code", I don't have the time and/or Cocoa knowledge to efficiently pitch in on this one. Or put another way, I don't have time to be a developer on every app that I use... %-/
I used to like Camino, and I might give it another whirl, but I've really gotten to like Firefox in many ways. I'm particularly hit by the lack of extensions or search plugins in Camino. In particular, the Web Developer Extension and Live HTTP Headers extension for FF are awesome if you have use for such things. The Sage RSS reader extension is also fairly nice.
There seems to be a half a beat pause after I first click a link (during the "contacting the website" phase), then the page almost instantly appears. In contrast, Safari begins rendering almost immediately, but takes half a beat to finish.
If you have a preference about how long the browser waits for data before it starts to render the data it already has, you can play with it in Camino (and Firefox) by typing about:config into the address window and editing "nglayout.initialpaint.delay". The value is in milliseconds and defaults to 250. If the parameter doesn't already exist create it by right-clicking and selecting New->Integer.
Obviously, this is one of those settings that is far too fine grained to put into a config box, so you just have to make a decision about what you think most users would want and go with it. But the about:config settings are there for the adventureous.
Looks like most of the dev being done on Bug 111230 is by all the guys from the Camino team.
There are some nice extra features (like the ability to easily edit the search field) in an addon called CaminTools.
I had the text overlap problem myself. For me, the solution was to check for duplicate fonts in your ~/Library/Fonts folder. There were several Microsoft web core fonts (like Arial) which duplicated OS X fonts of the same name. I dragged the extra .ttf files out of the folder and both Firefox and Camino have looked great ever since.
The relevant links are 316366 and 288047. Links to bugzilla from slashdot are blocked, so you might have to copy/paste the urls.
From the Features page: I'm not entirely clear how it works, or whether the blocklist is updatable, but there is also a freeware add-on called CamiBlock which allows you to import a blocklist (so I suppose you could use Filterset.G?).
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
CamiBlock has been superseeded by CamiTools: http://www.nadamac.de/camitools/index.php