Mozilla 2:Embedding APIs: Difference between revisions
Jump to navigation
Jump to search
MarkFinkle (talk | contribs) (Added notes) |
m (→Choices: formatting so that the major numbering shows up correctly) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
< [[Mozilla 2]] | |||
==== Choices ==== | ==== Choices ==== | ||
| Line 5: | Line 7: | ||
## WebKit/WebCore APIs for Mac OS X | ## WebKit/WebCore APIs for Mac OS X | ||
## 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]). | ## 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. | # Hybrid approaches, e.g. | ||
## Use MSHTML COM APIs for embedding, navigation, etc. but use standard DOM (XP)COM APIs for the DOM. | ## Use MSHTML COM APIs for embedding, navigation, etc. but use standard DOM (XP)COM APIs for the DOM. | ||
| Line 16: | Line 16: | ||
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=== | ===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. | 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) | [[User:MarkFinkle|MarkFinkle]] 22:19, 9 March 2007 (PST) | ||
[[Category:Mozilla 2]] | |||
Latest revision as of 10:50, 7 June 2007
Choices
- Use OS-default or otherwise dominant embedding APIs
- Epiphany's Gecko GTK widget for Gnome
- WebKit/WebCore APIs for Mac OS X
- MSHTML COM APIs for Windows, or .NET equivalents if necessary (we should strive to maintain, and even to extend, Adam Lock's work).
- Use a cross-platform embedding API
- Our own XPCOM-based API set
- WebKit/WebCore APIs
- 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.
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. MarkFinkle 22:19, 9 March 2007 (PST)