Create Task
Maniphest T10502

Define Phone IOUP
Open, NormalPublic
Actions

Description

The phone input-output usage pattern describes how KWin/Plasma behaves on phones.

Hardware characteristics

  • Primary input device is a touch screen.
  • Outputs are small displays (ca. 5'' diameter). Viewing distance to displays is low to very low (around 10 - 50cm)

KWin

Window behavior

  • Initial placement is Maximizing.
  • Window geometry can not be changed (but they can be moved to other screens).
  • Windows stack always according to most recently activated.

Window decorations

  • Decorations are not painted.

Internal windows

  • Window switcher (TabBox) is full-screen and shows stack or one-dimensional list (like current default one).
  • Virtual Keyboard fixated at the bottom edge of output, spans whole width and ca. 25%-75% of height. Active client must be resized or ignore the VK-covered area of its window.

Scale

  • For 1080p it is 2?

Plasmashell

  • Minimal panel with basic command buttons: Back, Home, Window Switcher
  • Full-screen application launcher on touch gesture (drag up from bottom edge).
  • Full-screen system tray on touch gesture (drag down from top edge).

Related Objects
Search...

romangg created this task.Feb 19 2019, 6:01 PM
romangg triaged this task as Normal priority.
nicolasfella added a comment.EditedFeb 19 2019, 6:07 PM

Window geometry can not be changed

Android has a split screen mode where two windows are tiled. If we wanted to supported that this assumption would not be true any more.

romangg added a comment.Feb 19 2019, 6:10 PM
In T10502#176600, @nicolasfella wrote:

Window geometry can not be changed

Android has a split screen mode where two windows are tiled. In this case this assumption would not be true.

That's true. We probably want something like this in PlaMo as well. It's basically a restricted tiling-window mode. How does it compare with tablets? Do you think it's the same or just about the "number of splits". I.e. on small phone like displays (~5'') maximal two, on tablets with larger screens (~10'') maximal 4.

nicolasfella added a comment.Feb 19 2019, 7:43 PM

For a large tablet a 3x2 split is also thinkable. What changes with the number of splits is the way they are controlled.

Other cases where the window geometry on the phone changes is when the screen is rotated or the virtual keyboard is pushing the window like @mart proposed

romangg added a comment.Feb 19 2019, 9:05 PM
In T10502#176649, @nicolasfella wrote:

For a large tablet a 3x2 split is also thinkable. What changes with the number of splits is the way they are controlled.

Right, but how is the way changed?

Other cases where the window geometry on the phone changes is when the screen is rotated or the virtual keyboard is pushing the window like @mart proposed

Virtual keyboard (VK) is a good point. The size and placement is probably also different on different IOUPs. On Desktop the VK should be kind of a movable window, which does not fill the whole screen (or it could be somewhat integrated in the window currently having keyboard focus). Windows and panels should be moved up, such that they are not covered by the VK. On Phones and Tablets the VK would just fill the lower ca. 25% - 75% of the screen and besides the currently (split) viewed windows no other client must change their size / integrate the keyboard.

romangg updated the task description. (Show Details)Feb 20 2019, 9:51 AM