Tokamak 6 takes place in Nuremberg, Germany from 16th to 22nd April, 2013 at the SUSE offices.
We need to figure out how to implement C++ plugins and export them. This is needed for dataengines, runners and a bunch of other things. It manifests itself in
After having gone through the C++ libplasma2 API, we should also do a review of our QML imports. API changes are documented here. (sebas) There's a number of open questions regarding the Plasma Quick 2 API:
There are a number of open questions such as:
Can we find a better solution for screen edge handling? How are we going to handle this in a Wayland world, where the compositor is the only thing which *can* know enough details for handling screen edge detection (for example for showing Plasma panels) correctly. (aseigo, mgraesslin)
Should we require KWin as compositor for Plasma2, possibly dropping support for other window managers? (aseigo, mgraesslin) Result: While practically, kwin will be the only wayland compositor for some time that actually implements the Shell interface, we will discipline ourselves to adhering to well-defined and documented interfaces, so we can, when that time arrives, standardize these things (for example popup placements) across different compositors.
Formalize how activities related to windows and virtual desktops. Currently there is often confusion and the KWin devs do not know how to properly implement and to recognize bugs. (see Bug 318153)
Should e.g. all non-default window switchers be moved to Plasma-Addons?
Plasma Theme showed problems for usage in KWin. Should we continue to use it or extend the theme to have specific elements for KWin's use cases (above all windows) - might overlap with "A Day At The Beauty Parlor".
Should we include a touch friendly decoration for not-maximized windows?
A full-screen mode would be useful for many Active Apps, so we need to define a "standard" way for apps to go full-screen. We need to ensure that it's always possible to return to windowed mode without the need for a physical keyboard or right mouse button, and even if the application hangs.
In which direction are we going to develop KRunner's overall architecture? Threading change, match updates / lifetime management, scheduling of init, teardown and match, AbstractRunner API might benefit from updates. (aseigo)
With plasma-shell, we are leaving behind the era of different binaries for different form factors and instead relying on runtime QML. Completing this experience with KWin, KRunner, etc. and defining how one switches between form factors needs to be laid down in detail. (aseigo)
Visual identity for PW2 (aseigo) @ http://www.wax-in-the-city.com ?