12-27-2012, 06:52 PM
silvarios wrote:
[quote=PeterB]
There are newer versions of the gecko engine which can be incorporated into Camino. Seamonkey uses just such a version.
I'm pretty sure this is incorrect. To clarify:
"Camino, like K-Meleon uses the embedding APIs to embed the Gecko rendering engine within a UI built with native widgets. Mozilla decided to kill off the embedding APIs because they were a drag on the rapid development needed to match Google Chrome. SeaMonkey, like Thunderbird, and Firefox is built on top of the XULRunner/toolkit framework and is unaffected by that decision."
Info from this thread, http://forums.mozillazine.org/viewtopic.php?f=6&t=2186387
Or straight from the horses mouth:
"While embedding has long been relatively low priority, being officially unsupported is a significant change. As important parts of embedding stop working, core Gecko contributors will longer be fixing them. Such breakages are unfortunately common—in fact, making sure that embedding breakages were resolved was a significant amount of the work that went into the release of Camino 2.0, as well as the upcoming Camino 2.1. Without support for embedding, releases of Camino using newer versions of Gecko—like the one used in Firefox 4—won’t be possible."
If you want to read the whole post, follow this link and scroll down to the post labeled "The Future of Camino".
That is inconsistent with this: http://en.wikipedia.org/wiki/Gecko_(layo...ine)#Usage
... scroll down and you'll see that Seamonkey is using the latest version of Gecko.
JEBB, try Seamonkey... it's similar to Camino in a lot of ways.