Hi When I was just about to choose Gecko as embedded web browser engine for my C++ application I was directed to this question on StackOverflow.com What is the best HTML Rendering Engine to embed in an application? (http://stackoverflow.com/questions/184373)
You can find there for example this statement: "When Apple was considering which engine to use in making Safari they looked at Gecko, but decided to go with KHTML, fork it and called it WebKit. Their reasons for doing this was that Gecko had tons of legacy cruft still leftover from Netscape and was far more complicated. KHTML/WebKit was newer, and thus had less legacy. It was also cleaner, quicker, and better documented." Can someone please comment on it? How much is it possible to avoid learning XPCOM when embedding Gecko? Are there any plans to hide/simplify use of XPCOM and get rid of old, legacy code? Regards Piotr Dobrogost _______________________________________________ dev-embedding mailing list dev-embedding@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-embedding
