Refactor: Extract UI Management from GeneralKeyboardIME to KeyboardUIManager

[bhanu-dev82]

Terms

• I have searched open and closed feature requests
• I agree to follow Scribe-Android's Code of Conduct

Description

The GeneralKeyboardIME class currently violates the Single Responsibility Principle by handling both the InputMethodService lifecycle and the detailed manipulation of the UI view bindings.

Currently, methods like updateUI(), setupIdleView(), setupToolbarView(), updateButtonVisibility(), and updateCommandBarHintAndPrompt() clutter the main service class.

Proposal

Create a new class KeyboardUIManager (or KeyboardLayoutHelper) that:

1. Takes the InputMethodViewBinding in its constructor.
2. Manages the state transitions (IDLE, SELECT_COMMAND, etc.) and updates the views accordingly.
3. Exposes simple methods like showIdleState() or showCommandState() that GeneralKeyboardIME can call.

Benefits

• drastically reduces the line count of GeneralKeyboardIME.
• Decouples UI logic from Service lifecycle.
• Makes it easier to change the UI layout in the future without breaking the service logic.

Contribution

I am happy to work on this refactor.

[angrezichatterbox]

@bhanu-dev82

Assigned the issue to you. Thanks for creating the issue :)