poetaster:
I’m not sure because I haven’t looked at it hard enough, but it is possible to stay closer to Silica like guidelines for design outside Silica. The main problem is that compositing with ambiences get’s us unified appearance, which no one else does. I would miss that. The way it’s done in the cases I deal with (Fahrplan for instance) is completely separate QML for the different platforms. That means more work, but with careful design, not necessarily so much more. And I’m working bit by bit at refactoring to make that more likely. If I was able to get a number of apps running on IOs, for instance, I might actually be able to finance the work
Well I guess the idea of making a Theme for Kirigami, and a QT_QPA_PLATFORMTHEME for Qt5.15 to make apps using those more Sailfish-like could help there.
So you develop against Kirigami, and use the “native” theme for depending on target platform.
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 compo…
I at one point made a promise to look into that, and did a) choose a name for the theme, SiO2, and b) write about seven lines of code and then stopped. I do not yet understand enough of what’s to be done here. (Commits · nephros/qtquickcontrols2 · GitHub , Commits · nephros/qtquickcontrols2-packaging · GitHub )
1 Like