Camino warning - Unresponsive script ???

[freeradical]

What is Gecko, and why can't future versions of Camino have it?

[silvarios]

freeradical wrote:
What is Gecko, and why can't future versions of Camino have it?

Gecko is the rendering engine behind Camino (Firefox as well).

http://www.cultofmac.com/89052/caminos-l...e-unclear/

[PeterB]

silvarios wrote:
[quote=PeterB]
Yes, Camino is getting a bit old, and I *wasn't* happy with what they did with v2.1.x and URL autocomplete behavior. The problem is that I've not seen a better browser, as far as simplicity and speed are concerned. Hopefully the developers get their act in gear...

There's not much that can be done. No more embedded Gecko means no more Camino. I suppose Camino could switch to Webkit.
Check out TGV's response in this thread, which sums up my response to that argument: http://hints.macworld.com/article.php?st...7205037991

[silvarios]

Huh? Camino lines up with Firefox 3.6, which is quite old. Camino cannot use a newer version of Gecko. That's all there is to it. Did you read the link I provided for freeradical? You can also find the same info on the Camino blog.

If you want development to continue, Camino developers will have to fork Gecko, switch to Webkit, or develop their own backend from scratch. Good luck.

[PeterB]

There are newer versions of the gecko engine which can be incorporated into Camino. Seamonkey uses just such a version.

[silvarios]

PeterB wrote:
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".

[JEBB]

Up until this script problem started Camino was a better choice for a browser than was Safari for my 2GB RAM MBA; it used up much less RAM. Would Seamonkey use less RAM as well?

[PeterB]

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.

[silvarios]

Actually, Wikipedia just confirmed what I already posted. SeaMonkey isn't using the same hooks as Camino. Seamonkey is fine, Camino is stuck. Again, Camino is not Seamonkey.

I'm surprised you haven't noticed the dearth of big updates in the last 18 months or so. Even if you missed the Mozilla and Camino announcements, surely the lack of such updates to the underlying engine should have been worrisome?

[silvarios]

PeterB wrote:
JEBB, try Seamonkey... it's similar to Camino in a lot of ways.

SeaMonkey is a modernization of the original Netscape/Mozilla suite. It is not using native widgets/interface and is certainly not a slimmed down browser. SeaMonkey contains a browser, mail client, HTML editor, and IRC client. Firefox would be more similar to Camino in comparison to SeaMonkey.

To be fair, SeaMonkey is not bloated when it comes to using computer resources as it is about the same as Firefox, which is pretty nice considering all the extra functionality.