Closed Bug 1163914 Opened 7 years ago Closed 6 years ago

Expose connected external display list to gaia system app

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: lchang, Assigned: kuoe0.tw)

References

Details

Attachments

(1 file, 4 obsolete files)

To avoid inventing a new API in this proof-of-concept stage, we propose using mozContentEvent/mozChromeEvent instead. Please refer to the Wiki [1] for our proposal.

[1] https://wiki.mozilla.org/Firefox_OS/1UA_Multi-Screen#Gaia
Assignee: nobody → lchang
Attached file WIP Patch (obsolete) —
Attach my WIP patch here.
Attached patch WIP patch (obsolete) — Splinter Review
Change format of the attachment.
Attachment #8605019 - Attachment is obsolete: true
Attachment #8605025 - Attachment description: 0001-Bug-1163914-Expose-connected-external-display-list-t.patch → WIP patch
We have similar functionality requirement for Presentation API device management and we've already create an API for it [1]. I think we can plug the external display to it without using mozChromeEvent.

[1] https://dxr.mozilla.org/mozilla-central/source/dom/webidl/PresentationDeviceInfoManager.webidl#17
Yes, we'll try merging multi-screen scenario into Presentation API eventually. For now, however, details aren't clear to us yet how to make it happen so we use mozChromeEvent temporarily until the spec is well-defined. What do you think?
Attached patch WIP patch (obsolete) — Splinter Review
Update my patch.
Attachment #8605025 - Attachment is obsolete: true
(In reply to Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz) from comment #3)
> We have similar functionality requirement for Presentation API device
> management and we've already create an API for it [1]. I think we can plug
> the external display to it without using mozChromeEvent.
> 
> [1]
> https://dxr.mozilla.org/mozilla-central/source/dom/webidl/
> PresentationDeviceInfoManager.webidl#17

Yes, integrate with Presentation API is one of our goals, but as we have discussed earlier, 1UA-multiscreen and Presentation API are far from integration, so we plan to stick on our current design (even though they are just for experiment) for the first phase. We will sure integrate with Presentation API in the future, thanks for pointing that out.
There are two individual parts for integrating into Presentation API, one for launching display and another for discovering display. The PresentationDeviceInfoManager is the later and is landed on master already. This API already implement an event passing mechanism, so you can write less code to fulfill your requirement. You can get this by hooking up the device list to PresentationDeviceManager in Bug 1133641, then you can avoid those shell.js hack. :)
Status: NEW → ASSIGNED
I've filed a task of integrating with PresentationDeviceInfoManager of Presentation API (Bug 1173263). Once it is done, System app no longer need to maintain a list of connected devices.
feature-b2g: --- → 2.2r+
After discussion with the team (Evelyn, Tommy, Luke), it's not really necessary to have this for flip phone's use case.
feature-b2g: 2.2r+ → ---
Attached patch Bug-1163914-hg.patch (obsolete) — Splinter Review
This patch will not land to m-c. This is a temporal method to demo multi-screen feature. I'll integrate the display list into device manager of Presentation API.
Assignee: lchang → kuoe0
Attachment #8605047 - Attachment is obsolete: true
Attachment #8642889 - Attachment is obsolete: true
Due to we'll integrate multi-screen feature into Presentation API. So, this bug can be closed. See Bug 1161440.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.