On Friday 20 January 2017, Dirk Hohndel wrote: > On Fri, Jan 20, 2017 at 05:06:40PM +0100, Tomaz Canabrava wrote: > > One option is to try to make next Subsurface the Subsurface 5: > > > > We have an *Awesome* dive log, and we can continue to develop that, or we > > can do a step back and try to change the *bare minimum* on the core to > > facilitate the integration on the Qml engine without code duplication, my > > take on that would be to port the C-Structs to C++ Classes that inherit > > from QObject (because we can fed those to QML), not messing with the > > algorithms nor anything else that we don't need to touch - those should > > still be in C, algougth compiled with a c++ compiler to have C++ linkage > > and we can call their code from QML, while also using those parts on the > > Desktop version reducing the amount of duplicated code. > > So let's see. > - we have a by and large usable desktop app, used by 10000+ people where > several developers feel they can make changes > - we have a piece of shit mobile app, used by a few hundred people, where > not a single developer feels they know what they are doing. > > I have spent something like 20 hours over the past few nights, trying to > get that pile of garbage to work with Kirigami 2 (since Kirigami 1 is > already abandoned). Which means switching to Controls.2. Which means > nothing works. I finally have this far enough that at least it opens on > Android, but it's completely broken.
just a couple of precisations: * we can still do bugfix releases of kirigami1, if we get clear bug reports of what is exactly going wrong * porting to kirigami2 does not mean having to move to QtQuickControls2, the two things are unrelated, it just happens to be based upon qtquickcontrols2, but it can be mixed with qtquickcontrols1 in every way -- Marco Martin _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
