On sábado, 13 de agosto de 2016 20:30:39 PDT Gunnar Roth wrote:
> >> b. adding EditorFont to qplatformtheme.h enumeration ,has also no risk.
> >
> > Not allowed per Qt API compatibility promise: code compiled with Qt 5.6.x
> > must run just fine with Qt 5.6.y even if y < x.
>
> Well thats
Hi Thiago,
thanks for you answers.
> Am 13.08.2016 um 20:05 schrieb Thiago Macieira :
>
> On sábado, 13 de agosto de 2016 18:08:16 PDT Gunnar Roth wrote:
>> 1. category is just adding code, which does not influence current
>> code.
>> a. adding qAsConst in qgolbal.h.
On sábado, 13 de agosto de 2016 18:08:16 PDT Gunnar Roth wrote:
> 1. category is just adding code, which does not influence current
> code.
> a. adding qAsConst in qgolbal.h. That is actually something i really
> like to have in qt 5.6, because it is very useful and has no risk.
Except that
Hi Thiago,
to make qt 5.6.x support the quick controls2 there are only a few changes
needed.
1. category is just adding code, which does not influence current code.
a. adding qAsConst in qgolbal.h. That is actually something i really like
to have in qt 5.6, because it is very useful and has
I don't see any need in distinguishing different OAuth implementations for
Qt -- once we have an "officially supported" Qt module, it'll be a default
opt-in for the user's code.
+1 for QtOAuth as a separate module
Regards,
Konstantin
2016-08-13 11:28 GMT+04:00 Sune Vuorela :
Sounds good to me.
We'll also need some days past the feature free to get the remaining changes to
the configuration system merged.
Cheers,
Lars
On 12 Aug 2016, at 21:31, Simon Hausmann
> wrote:
Hi,
I totally support Kai's request.
On the
On 2016-08-12, Fredrik de Vibe wrote:
> We have recently been working on an implementation of OAuth (1+2), and
> this is now approaching a state in which it can be distributed as a tech
> preview. For this we'll need a new public repository.
there is a handful of external