John Hu [:johnhu][:johu][:醬糊小弟] Reporter
	Description • 11 years ago

Two-layered widget support is based on current two layered OOP mechanism.

The UI/window of widget is created and managed by System app. But the layout of widget is designed by custom Homescreen app. System lays out them as the following sequence: 1. group div of homescreen, 2. homescreen iframe, 3. widget iframe (the later the higher).

All input events to widget should be blocked by system app. But all input events to Homescreen app should be passed through.

	John Hu [:johnhu][:johu][:醬糊小弟] Reporter
	Comment 1 • 11 years ago

Gene,

I don't think we need to depend on bug 819882 because the widget is opened by System app not Homescreen app.

	Gene Lian (I already quit Mozilla)
	Comment 2 • 11 years ago

Sure! Which one do you think we should make bug 819882 depend on?

	John Hu [:johnhu][:johu][:醬糊小弟] Reporter
	Comment 3 • 11 years ago

The three-layered version needs it. But we don't have it, now.

	Gene Lian (I already quit Mozilla)
	Comment 4 • 11 years ago

As far as I know from you guys, you need open-window-remote to open bookmarks on the homescreen. Right? It's not a matter of two or three layers.

	John Hu [:johnhu][:johu][:醬糊小弟] Reporter
	Comment 5 • 11 years ago

Yes, right. But we use window.open to open bookmark which is also handled by system app instead of creating an Iframe in homescreen app.

	Gene Lian (I already quit Mozilla)
	Comment 6 • 11 years ago

Yeap, just wonder is there any good Stingray bug to set the dependency on it?

	John Hu [:johnhu][:johu][:醬糊小弟] Reporter
	Comment 7 • 11 years ago

Since the prototype of 2-layered doesn't land to master, we need invalid this bug.

The prototype of 2-layered can be found at: https://github.com/luke-chang/gaia/tree/TV_arch1

We will build a hybrid model which won't use IAC anymore and new bugs for hybrid model will be created.