Camino is NOT built on top of XULRunner, unless something very fundamentally changed since I last looked at the code.
In fact, many of the problems we've had arise from the fact that it has lots of dependencies inside core Gecko that are thought to be private interfaces.
Tristan
· 2 years ago
Great post, John!
John
· 2 years ago
Håkan W, you're right, absolutely. I'm being a little loose here, and should be talking about building on top of Gecko instead of XULrunner, but yesterday conflated using the codebase integrated to build other apps with the XULrunner runtime.
Lori
· 2 years ago
"We do have to make choices, though. There’s only so much time, there’s only so much attention. It’s tough for a small band of folks to change the world, and sometimes you do things in an order you may not like the best." So funny -- it's something we tell our users (and especially our beta testers) over and over again, and I work for one of the Big Moneythrowers mentioned above. :) The Company may be huge, but the development teams are relatively small -- and the releases must be well-defined, manageable, and (above all, when you work for a for-profit organization) shippable. Gah, I could write pages and pages on this subject, but I don't want to hijack your comments. Maybe I'll post about it in my blog, or the new team one, one of these days...
muhabbet
· 1 year ago
Thank you very much for this useful article and the comments.
--------------- Leonard The Magazine Stundent at 9 Eylul University sohbet
All Comments
In fact, many of the problems we've had arise from the fact that it has lots of dependencies inside core Gecko that are thought to be private interfaces.
---------------
Leonard The Magazine Stundent at 9 Eylul University sohbet