995835 - [System][LockScreen] Extend LockScreenWindowManager to communicate with the LockScreen app

Status: RESOLVED DUPLICATE of bug 898348

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[Greg Weng [:snowmantw][:gweng][:λ]]

Discussed with Tim, that:

System should have a LockScreenManager to programmatically unlock or lock the screen, and pass such related events like |screenchange| and |ftuopen| to the app if necessary (some of them are only for System app).

However, since we already have the LockScreenWindowManager, to create more managers seems making System app more complicated. So we may extend the LockScreenWindowManager to manage the events. The new manager would take all LockScreen related events, including those programmatically unlocking or locking requests, and forward them as |request-lock| and |request-unlock| message to the LockScreen app via IAC, and to control the window to open or close it simultaneously.

Comment 1

[Greg Weng [:snowmantw][:gweng][:λ]]

CC alive to see if he has some more opinions.

Comment 2

[Greg Weng [:snowmantw][:gweng][:λ]]

CC -> NI

Comment 3

[(inactive after 6/18) Alive Kuo [:alive]]

Makes sense. The event handling part in lockscreen.js should be moved into lockscreenWindowManager.

Comment 4

[howie [:howie]]

to be done together with bug 898348