On 04. aug. 2015 10:43, Eskil Abrahamsen Blomfeldt wrote:
Hi,
Qt Purchasing is a commercial add-on module developed by The Qt Company
which implements a cross-platform API for in-app purchases on iOS and
Android. In order to make it easier for third parties to contribute new
backends for the A
Will Qt Purchasing be included in Qt 5.6? If so, will binaries be pre-built
or will users be required to manually build them for each platform?
Steve
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mail
On Thu, Aug 6, 2015 at 1:53 PM, Steve G wrote:
> I see no reason why open source users have to build the Qt Purchasing module
> manually and it can't be available as part of the build process, especially
> as there may be many users who may not know how to build it.
Because this thread is questio
Sent: Thursday, August 6, 2015 5:38 AM
To: development@qt-project.org
Subject: Re: [Development] Qt Purchasing in Qt 5.6
On 08/05/2015 04:54 PM, Thiago Macieira wrote:
> The Qt Project cannot do otherwise. There isn't enough time and the module
> is
> 5 weeks late.
>
> I'
Or make it a technical preview ... It is non-crucial "nice to have" *that will
make a lot of people happy* feature;-).
Cheers,
BogDan.
On Wednesday, August 5, 2015 6:50 PM, Thiago Macieira
wrote:
On Wednesday 05 August 2015 15:33:10 BogDan wrote:
> In this case IMHO we should delay the
On Wednesday 05 August 2015 15:33:10 BogDan wrote:
> In this case IMHO we should delay the feature freeze (and the release)
> with 5 weeks or to make it an optional technical preview with no API/ABI
> back compatibility promises. Qt Purchasing library is not crucial a crucial
> library that we ca
On Wednesday 05 August 2015 07:53:40 Knoll Lars wrote:
> >The release team decided the new modules should be released under
> >Technical
> >Preview for 5.6 (they came in 5 weeks past the deadline that Jani sent).
> >So
> >there's no rush in reviewing the API right now, as we've given us time to
>
On 08/05/2015 01:08 PM, Marc Mutz wrote:
> On Wednesday 05 August 2015 09:59:52 Oswald Buddenhagen wrote:
>>> How do we handle reviews beyond that? Should I make a patch to qt5.git
>>> and collect comments there, or would it be better if I make a mock
>>> change that includes the entire code base s
On Wednesday 05 August 2015 09:59:52 Oswald Buddenhagen wrote:
> > How do we handle reviews beyond that? Should I make a patch to qt5.git
> > and collect comments there, or would it be better if I make a mock
> > change that includes the entire code base so that we can get inline
> > comments? I
> On Aug 5, 2015, at 1:43 AM, Eskil Abrahamsen Blomfeldt
> wrote:
>
> On 08/05/2015 09:31 AM, Knoll Lars wrote:
>
>> Well, let’s create the repository today and import the codebase so
>> everybody can have a look.
>
> Done!
>
> The code is now in
> https://codereview.qt-project.org/#/admin/
On 08/05/2015 09:31 AM, Knoll Lars wrote:
> Well, let’s create the repository today and import the codebase so
> everybody can have a look.
Done!
The code is now in
https://codereview.qt-project.org/#/admin/projects/qt/qtpurchasing
I'll make a patch for qt5.git as well and collect comments on
On Wed, Aug 05, 2015 at 09:31:15AM +0200, Eskil Abrahamsen Blomfeldt wrote:
> The module has also been in active use for a while. My plan was to
> upload the whole history including the peer reviews (mostly done by
> Andy Nichols and me).
>
upload from where? and what exactly do you mean by "revie
On 05/08/15 09:35, "Thiago Macieira" wrote:
>On Wednesday 05 August 2015 09:31:15 Eskil Abrahamsen Blomfeldt wrote:
>> It's not huge and all changes have been through peer reviews already
>>(by
>> approvers in the Qt Project). The module has also been in active use
>>for
>> a while. My plan was
On Wednesday 05 August 2015 09:31:15 Eskil Abrahamsen Blomfeldt wrote:
> It's not huge and all changes have been through peer reviews already (by
> approvers in the Qt Project). The module has also been in active use for
> a while. My plan was to upload the whole history including the peer
> rev
On 08/04/2015 04:12 PM, Thiago Macieira wrote:
> On Tuesday 04 August 2015 10:43:35 Eskil Abrahamsen Blomfeldt wrote:
>> Hi,
>>
>> Qt Purchasing is a commercial add-on module developed by The Qt Company
>> which implements a cross-platform API for in-app purchases on iOS and
>> Android. In order to
On 04/08/15 21:57, "Jake Petroules" wrote:
>
>> On Aug 4, 2015, at 7:12 AM, Thiago Macieira
>>wrote:
>>
>> On Tuesday 04 August 2015 10:43:35 Eskil Abrahamsen Blomfeldt wrote:
>>> Hi,
>>>
>>> Qt Purchasing is a commercial add-on module developed by The Qt Company
>>> which implements a cross-p
> On Aug 4, 2015, at 7:12 AM, Thiago Macieira wrote:
>
> On Tuesday 04 August 2015 10:43:35 Eskil Abrahamsen Blomfeldt wrote:
>> Hi,
>>
>> Qt Purchasing is a commercial add-on module developed by The Qt Company
>> which implements a cross-platform API for in-app purchases on iOS and
>> Android.
Hi,
I can review the Android part.
Cheers,BogDan.
On Tuesday, August 4, 2015 5:12 PM, Thiago Macieira
wrote:
On Tuesday 04 August 2015 10:43:35 Eskil Abrahamsen Blomfeldt wrote:
> Hi,
>
> Qt Purchasing is a commercial add-on module developed by The Qt Company
> which implements a
On Tuesday 04 August 2015 10:43:35 Eskil Abrahamsen Blomfeldt wrote:
> Hi,
>
> Qt Purchasing is a commercial add-on module developed by The Qt Company
> which implements a cross-platform API for in-app purchases on iOS and
> Android. In order to make it easier for third parties to contribute new
>
Hi,
Qt Purchasing is a commercial add-on module developed by The Qt Company
which implements a cross-platform API for in-app purchases on iOS and
Android. In order to make it easier for third parties to contribute new
backends for the API, we want to release it in the Qt Project under
LGPLv3/G
20 matches
Mail list logo
