Confirmed users
180
edits
Embedding/IPCLiteAPI: Difference between revisions
Jump to navigation
Jump to search
→Lite-weight Embedding API for Mozilla based applications with native UI.
| Line 1: | Line 1: | ||
== Lite-weight Embedding API for Mozilla based applications with native UI. == | == Lite-weight Embedding API for Mozilla based applications with native UI. == | ||
<p>Basic architecture is very close to [http://trac.webkit.org/wiki/WebKit2 WebKit2], and [http://browser.garage.maemo.org/docs/browser_paper.html MicroB] | <p>Basic architecture is very close to [http://trac.webkit.org/wiki/WebKit2 WebKit2], and [http://browser.garage.maemo.org/docs/browser_paper.html MicroB] | ||
== Story == | |||
=== Mozilla has bunch of technologies integrated recently: === | |||
* [https://wiki.mozilla.org/Platform/GFX/OffMainThreadCompositing OMTC - Off Main thread compositing - keeping Gecko/XPCOM and Compositor in separate threads (Android Firefox)] | |||
* [https://wiki.mozilla.org/Electrolysis IPC - Multiprocess rendering - keeping Gecko/XPCOM and Compositor in separate processes (Firefox OS, Desktop Firefox Plugins)] | |||
In order to build Simple browser with native UI (Gtk/Qt/UiKit) similar to Android Firefox with Java UI, some internal API need to be exposed. | |||
Goal of this project to provide Generic embedding API which could be easily wrapped without bunch of extra code into Toolkit specific Widgets, and embed these widgets into platform UI applications. | |||
</p><p>Benefits of new architecture comparing to default [https://wiki.mozilla.org/Embedding/NewApi mozilla embedding]:</p> | </p><p>Benefits of new architecture comparing to default [https://wiki.mozilla.org/Embedding/NewApi mozilla embedding]:</p> | ||
<pre class="_fck_mw_lspace">* No XUL/XPCOM heavy content in UI process/Thread (Best memory footprint (process case), fast startup) | <pre class="_fck_mw_lspace">* No XUL/XPCOM heavy content in UI process/Thread (Best memory footprint (process case), fast startup) | ||