With Qt5.15/KF5 project, we are progressing fast in terms of packaging new libraries. Based on the progress so far, we can conclude that, what started as a proof-of-concept, works and it is possible to have Qt 5.15 on our devices. Thus, it is natural to ask what to do next with this.
From SFOS point of view, we are kept behind by proprietary packages. So, one way of approaching this is to replace all proprietary code with the open source alternatives. This includes Silica, SFOS compositor components, email client, accounts handling, keyboard components to name few. This is surely not a small task, but we donāt have to fix it immediately either. Silica apps can run on newer Qt Wayland based compositors as well - not perfect in terms of app background, but possible. So, it is possible to start replacing components one by one if we go for a full revamp.
Another approach would be to bring apps over and try to integrate them better with SFOS. This could include styling in terms of themes (QT_QPA_PLATFORMTHEME
) and Kirigami.
The both approaches (revamp and integration) could easily coexists and its up to us, developers, to choose what we prefer to spend our time on.
Coming back to full revamp, if we go for it, we should target full compatibility with Plasma apps. So, we could basically take Plasma app and run it unchanged on SFOS. Same goes for SFOS apps on Plasma. To preserve or to evolve based on SFOS designs, we should style apps accordingly. However, if we compare interactions of Kirigami (used by Plasma) to Silica, it is clear that Kirigami has larger number of them and we would have to make some choices regarding what to map and what to keep as it is. Use Kirigami Gallery demo app at Chum to see what is available. In particular, menus on the left (global) and right (context) have frequently more items that would make sense to add to pulley menus (leaving page actions for them pulley menus?). On the other side, if menus stay as they are, left and right swipe gestures are taken by them an compositor would have avoid using them.
In case of full revamp, compositor is surely something that has to be addressed. Not knowing much about Lipstick (is it simple to port to Qt5.15/Qt6) and Plasmaās KWin, it is hard to choose. Ideally, we should try to reuse as much software where we can share the load with others. So, maybe KWin styling can be considered. KWin has dropped hwcompositor, but patches exist to bring it back.
On Plasma Mobile side, as far as we know, the major gaps are in email and possibly calendar software - something that we have used to have in a rather good quality. As far as I know, we have parts that are open-source and proprietary. So, it maybe of interest for Plasma folks and maybe we can work together on some mix of the solutions.
While working on a strategy, it is important to figure out Jollaās expectations and plans. We rely on Jollaās infrastructure and great relations with their developers. Something, that we want to keep and rely upon. How could Jolla benefit from it? What would be the ways for them to ensure that they can sell their products? Unfortunately, Jolla tends to be rather quiet regarding their plans. So, we can either hope that they would open up a bit or we would have to guess the pathways.
On behalf of myself and @piggz.