Closed
Bug 567703
Opened 15 years ago
Closed 14 years ago
Integrate electrolysis (e10s) into Jetpack SDK
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: myk, Assigned: avarma)
References
Details
Attachments
(2 files)
104.90 KB,
application/x-xpinstall
|
Details | |
67.32 KB,
patch
|
warner
:
review+
|
Details | Diff | Splinter Review |
We should figure out a strategy for integrating electrolysis (e10s) into the Jetpack SDK, including which parts of the APIs are going to live in the chrome process vs. separate addon processes, how to give addons access to content DOM objects (window, document, etc.), and what changes will need to be made to the existing and forthcoming APIs to render them e10s-compatible.
Atul says he can take this on and work with the e10s team to work through these issues, so assigning this bug to him.
Updated•15 years ago
|
Priority: -- → P1
Target Milestone: -- → 0.5
Version: unspecified → Trunk
Comment 1•14 years ago
|
||
This is the hacked-up XPI we did tonight as a PoC.
* The main module is configured as remote-main.js instead of main.js
* That hardcodes some paths to launch the remote process and set up message receivers for it, and load the "real" jetpack main into it.
* remote-core.js is basically "hacky cuddlefish for the jetpack process", and for now I just hard-coded module impls for widget and xhr.
Assignee | ||
Comment 2•14 years ago
|
||
Thanks Benjamin! I've created a jetpack package that does roughly the same thing, which warner, irakli and I used as a springboard for discussion on Friday:
http://github.com/toolness/oop-jetpack-sdk-poc
I'll write up a summary of what we discussed and post it as either a blog post or a forum post to the google group, I think.
Updated•14 years ago
|
Target Milestone: 0.5 → --
Assignee | ||
Comment 3•14 years ago
|
||
Latest update on this is here:
http://github.com/toolness/jetpack-e10s/#readme
Assignee | ||
Comment 4•14 years ago
|
||
I'm now working on a patch to get the changes into the SDK:
http://github.com/toolness/jetpack-sdk/tree/e10s
Status: NEW → ASSIGNED
Summary: figure out strategy for integrating electrolysis (e10s) into Jetpack SDK → Integrate electrolysis (e10s) into Jetpack SDK
Assignee | ||
Comment 5•14 years ago
|
||
Note that Brian Warner and I are currently pair-programming on the above branch.
Assignee | ||
Comment 6•14 years ago
|
||
Assignee | ||
Comment 7•14 years ago
|
||
Comment on attachment 487062 [details] [diff] [review]
Final patch
This patch is taken from all the changesets in this github branch:
http://github.com/toolness/jetpack-sdk/tree/e10s
From the branch's inception, up to and including commit 4c768aa5e004e3efb45b1608559be69e969702fc.
The code was all pair programmed by warner and I; I'd take the driver's seat when we were changing code that warner knew best, and vice versa.
Some of the code was written solo by me, but we synchronously code reviewed it together.
Attachment #487062 -
Flags: review?(warner-bugzilla)
Comment 8•14 years ago
|
||
Comment on attachment 487062 [details] [diff] [review]
Final patch
awesome!
Attachment #487062 -
Flags: review?(warner-bugzilla) → review+
Comment 9•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 10•14 years ago
|
||
WOO! congrats on getting this landed!
Reporter | ||
Comment 11•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.
To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•