Closed Bug 1074749 (input-window) Opened 10 years ago Closed 7 years ago

[Tracking] Implement InputWindow and InputWindowManager (originally KeyboardWindowManager)

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mnjul, Unassigned)

References

Details

Let's implement InputWindow and InputWindowManager. An InputWindow instance is the wrapping object of a Keyboard App frame, which is currently book-kept in |InputFrameManager.runningLayouts|. InputWindowManager will probably follow our current interface exposed with AppWindowManager. This probably will move quite some code from current KeyboardManager. InputWindow will also utilize AppTransitionController for transition (probably through inheritance from AppWindow). If possible, that should eradicate the need for InputAppTransitionManager. If done nicely, after this bug (which we'll probably want to carry out with smaller sub-bugs), we'll see a KeyboardManager that has been stripped to nearly nothing (and maybe we could rightfully rename it to be InputMethodManager?), and the transformation of InputFrameManager (into InputWindowManager) and InputAppTransitionManager (into what's already supported by AppTransitionController).
Depends on: 1075306
FYI some planning stuffs are getting drafted in bug 1075306 comment 5
Depends on: 1091509
Depends on: 1093477
Depends on: 1093537
Depends on: 1097446
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.