On Fri, Jul 20, 2012 at 10:48 AM, Marco Martin <[email protected]> wrote: > On Friday 20 July 2012, Alex Fiestas wrote: >> On Thursday 19 July 2012 21:18:50 Marco Martin wrote: >> > anybody can think about technical problems about it that may be lurking? >> > it may mean a release of the workspace that doesn't use completely >> > frameworks, so both old kdelibs and the frameworks will have to be >> > distributed for some time, may this be a problem? (but not avoidable >> > probably) >> >> Uh... please don't eat me :) >> >> Do we really want to support qgv? it is a super big chunk of code we will >> have to maintain for, waht gain? >> > > keep in mind the instant the qgv part is dropped 100% of the shells, all > plasmoids, all bindings and a good chunk of 3rd party plasmoids needs to be > ported (and i would be surprised if the qml1 plasmoids would work in a qml2 > version without being touched) > so dropping the qgv part even if really applealing from the developer pov (it > would solve quite some problems) is not feasible, because it really means > another 4.0 :/ > > it will probably take years, in which probably a qml2 shell will coexist > without being released for the use by developers > > -- > Marco Martin > _______________________________________________ > Plasma-devel mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/plasma-devel
Well, can we even mix qtquick 1 and qtquick 2? Aleix _______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
