On Wed, May 15, 2019 at 07:50:42PM +0200, André Pönitz wrote:
> On Wed, May 15, 2019 at 11:38:25AM +0200, Oswald Buddenhagen wrote:
> > [...]
> > jake had started that "qt-free qbs" project (he got as far as
> > eliminating (most) use of qt containers), but it was snuffed out because
> > it was
On Thu, May 16, 2019 at 10:00:33AM +1200, Christian Gagneraud wrote:
> On Thu, 16 May 2019 at 09:32, Иван Комиссаров wrote:
> > > 15 мая 2019 г., в 19:50, André Pönitz написал(а):
> > >
> > > Getting rid of implicitly shared containers should be a rather obvious
> > > move
> > > when
??
Gesendet: Donnerstag, 16. Mai 2019 01:25
An: Christian Gagneraud
Cc: qbs
Betreff: Re: [Qbs] Donation to QBS developers/maintainers/contributes
In many cases, you don’t need to copy them. For trivial getters, you can return
const-ref/span to the internal vector instead of a copy becaus
On Thu, 16 May 2019 at 11:24, Иван Комиссаров wrote:
>
> In many cases, you don’t need to copy them. For trivial getters, you can
> return const-ref/span to the internal vector instead of a copy because in
> many places all we do is iterate over that vector.
>
> The only argument for copies is
In many cases, you don’t need to copy them. For trivial getters, you can return
const-ref/span to the internal vector instead of a copy because in many places
all we do is iterate over that vector.
The only argument for copies is that it’s impossible to change the
implementation from returning
On Thu, 16 May 2019 at 09:32, Иван Комиссаров wrote:
> > 15 мая 2019 г., в 19:50, André Pönitz написал(а):
> >
> > Getting rid of implicitly shared containers should be a rather obvious move
> > when "performance" is part of any "final picture", coherent or not.
>
> +1 from me, hidden detaches
+1 from me, hidden detaches are evil =)
> 15 мая 2019 г., в 19:50, André Pönitz написал(а):
>
> Getting rid of implicitly shared containers should be a rather obvious move
> when "performance" is part of any "final picture", coherent or not.
>
> Andre'
>
On Wed, May 15, 2019 at 11:38:25AM +0200, Oswald Buddenhagen wrote:
> [...]
> jake had started that "qt-free qbs" project (he got as far as
> eliminating (most) use of qt containers), but it was snuffed out because
> it was unrealistic and counterproductive at that time. even now, no
> patches in
On Tue, May 14, 2019 at 04:17:41PM +0200, Иван Комиссаров wrote:
> Qbs itself has a huge dependency on a QtCore, but some stuff is
> present in standard library and can be easily changed to that (we
> still have enourmous amount of places where qlist is used instead of a
> qvector/std::vector and
Good information, thanks.
Qbs itself has a huge dependency on a QtCore, but some stuff is present in
standard library and can be easily changed to that (we still have enourmous
amount of places where qlist is used instead of a qvector/std::vector and used
inefficient); others are trickier but
On Tue, 14 May 2019 at 23:11, Christian Gagneraud wrote:
>
> On Tue, 14 May 2019 at 22:51, Иван Комиссаров wrote:
> >
> > I wonder how hard is to implement pure c++ "declarative" library. Afaik,
> > qtdeclarative originally used v8 JavaScript engine which got replaced with
> > Qt-ish engine to
On Tue, 14 May 2019 at 22:51, Иван Комиссаров wrote:
>
> I wonder how hard is to implement pure c++ "declarative" library. Afaik,
> qtdeclarative originally used v8 JavaScript engine which got replaced with
> Qt-ish engine to avoid conversions to/from Qt types. Maybe, it's possible to
> go the
I wonder how hard is to implement pure c++ "declarative" library. Afaik,
qtdeclarative originally used v8 JavaScript engine which got replaced with
Qt-ish engine to avoid conversions to/from Qt types. Maybe, it's possible to go
the opposite direction and remove Qt dependency in the first place?
>> However, will this help to get new developers? Right now, there are not that
>> many contributors.
>
> I agree, how much money do you want to raise? And what for?
> For now Qbs can use Qt (company/project) infra, so there's no need to
> manage an infra.
The Qt Company pays for qt.io. We can
> If I am right, one urgent task is to remove the dependency of Qt Script.
I don't think it's urgent. It might not even be necessary given that Qbs won't
be Qt's next build system and won't have to be bootstrapped. But if you have
good ideas, feel free to discuss in
If I am right, one urgent task is to remove the dependency of Qt Script.
Vincent
On Tue, 14 May 2019 at 17:51, Christian Gagneraud wrote:
> On Tue, 14 May 2019 at 21:46, Иван Комиссаров wrote:
> >
> > +1
> >
> > However, will this help to get new developers? Right now, there are not
> that
On Tue, 14 May 2019 at 21:46, Иван Комиссаров wrote:
>
> +1
>
> However, will this help to get new developers? Right now, there are not that
> many contributors.
I agree, how much money do you want to raise? And what for?
For now Qbs can use Qt (company/project) infra, so there's no need to
+1
However, will this help to get new developers? Right now, there are not that
many contributors.
Иван Комиссаров
> 14 мая 2019 г., в 11:18, Карелин Павел написал(а):
>
> +1
>
> 14.05.2019 11:54, Алексей Скородумов пишет:
>> Hi,
>>
>> Is it hard to make "donate" button on "QBS site" as a
+1
14.05.2019 11:54, Алексей Скородумов пишет:
Hi,
Is it hard to make "donate" button on "QBS site" as a part of
"transition to community"?
I can't contribute time right now, but would like to support the project.
--
Best regards,
Aleksei Skorodumov
19 matches
Mail list logo
