Mozilla 2:Embedding APIs: Difference between revisions

m
→‎Choices: formatting so that the major numbering shows up correctly
m (→‎Choices: formatting so that the major numbering shows up correctly)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
< [[Mozilla 2]]
==== Choices ====
==== Choices ====


Line 4: Line 6:
## Epiphany's Gecko GTK widget for Gnome
## Epiphany's Gecko GTK widget for Gnome
## WebKit/WebCore APIs for Mac OS X
## WebKit/WebCore APIs for Mac OS X
## MSHTML COM APIs for Windows, or .NET equivalents if necessary
## MSHTML COM APIs for Windows, or .NET equivalents if necessary (we should strive to maintain, and even to extend, [http://www.iol.ie/~locka/mozilla/mozilla.htm Adam Lock's work]).
 
# Use a cross-platform embedding API
# Use a cross-platform embedding API
## Our own XPCOM-based API set
## Our own XPCOM-based API set
## WebKit/WebCore APIs
## WebKit/WebCore APIs
## MSHTML?  Non-starter on non-Windows, I think
## MSHTML?  Non-starter on non-Windows, I think
# Hybrid approaches, e.g.
## Use MSHTML COM APIs for embedding, navigation, etc. but use standard DOM (XP)COM APIs for the DOM.


Contributions welcome here, please start and cite (with Google Groups links) newsgroup threads as needed.
Contributions welcome here, please start and cite (with Google Groups links) newsgroup threads as needed.


/be
[[User:Brendan|/be]]
 
===Notes===
Using the OS-Default may also have the benefit of easier development for embedders. For example, on Windows, C++ APIs are not the easiest to work with anymore. C# and .NET languages would favor .NET wrapper or COM wrapper.
[[User:MarkFinkle|MarkFinkle]] 22:19, 9 March 2007 (PST)
 
[[Category:Mozilla 2]]
3

edits