On Freitag, 30. September 2016 15:43:57 CEST Shawn Rutledge wrote:
> Back in Nokia times it was said that we shouldn't use semicolons, because it
> would speed up the parsing and reduce the size of resources slightly. [...]
Back in Nokia times, someone was reviewing a patch and made a comment that
On Fri, Sep 30, 2016 at 4:43 PM, Shawn Rutledge wrote:
> On 30 Sep 2016, at 14:19, Kai Koehne wrote:
>> To make a proposal: Let’s use semicolons in imperative JS parts of QML in
>> our examples and documentation
>
> Back in Nokia times it was said that we shouldn't use semicolons, because it
>
On Fri, Sep 30, 2016, at 11:00 PM, Kai Koehne wrote:
> Interesting. Indeed, I wouldn't have thought it makes any measurable
> difference. IIRC we had a qml mimizer once, I guess this is still around?
tools/qmlmin in qtdeclarative
> It's certainly not that important to me that I will spend a day o
On Fri, Sep 30, 2016 at 03:43:57PM +, Shawn Rutledge wrote:
> On 30 Sep 2016, at 14:19, Kai Koehne wrote:
> > To make a proposal: Let’s use semicolons in imperative JS parts of QML in
> > our examples and documentation
>
> Back in Nokia times it was said that we shouldn't use semicolons, beca
>> To make a proposal: Let’s use semicolons in imperative JS parts of QML in
>> our examples and documentation
>
> Back in Nokia times it was said that we shouldn't use semicolons, because it
> would speed up the parsing and reduce the size of resources slightly. (Maybe
> you think performance
On sexta-feira, 30 de setembro de 2016 08:26:13 PDT Thiago Macieira wrote:
> For example, to switch to dev, I might do:
>
> git submodule foreach "git rev-parse origin/dev && \
> git rebase --onto origin/dev origin/5.8 || true"
By the way, on my Windows and Mac machines, since they fetch
On 30 Sep 2016, at 14:19, Kai Koehne wrote:
> To make a proposal: Let’s use semicolons in imperative JS parts of QML in our
> examples and documentation
Back in Nokia times it was said that we shouldn't use semicolons, because it
would speed up the parsing and reduce the size of resources sligh
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Sean Harmer
> Sent: Friday, September 30, 2016 12:39 PM
> To: development@qt-project.org
> Subject: [Development] Managing branches of Qt's git modules
>
> Hi,
>
> just
On sexta-feira, 30 de setembro de 2016 11:39:20 PDT Sean Harmer wrote:
> So, what do people do to checkout all interesting modules to 5.7, 5.8,
> dev etc on Unix like systems and on Windows?
>
> On *nix systems I've been getting away with a simple bash for loop. But
> on windows I find this painfu
On Freitag, 30. September 2016 12:19:09 CEST Kai Koehne wrote:
> Hi,
>
> It’s Friday, so time for some bikeshedding ;)
>
>
> As you might know, the semicolon as a statement separator in JavaScript is
> optional.
Technicly, that's more complicated than that. The semicolons are mandatory.
But i
I am also already abiding to the practice of using semicolons between curly
braces and no semicolons for simple bindings.
Marco Piccolino
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
FWIW, in unity8 (reasonably big QML application) we agreed to not use
semicolons for declarative code unless you really want to write some
things into a single line and need them, but always use semicolons for
imperative code.
This has served us very well over the past years, seems consistent and
I personally use semicolons always when {} is incorporated. And {} I'm using
when its more than a single statement.
Beste Grüße / Best regards,
Alexander Nassian, bitshift dynamics GmbH___
Development mailing list
Development@qt-project.org
http://lists
4. If the semicolon makes you feel angry, feel free to arbitrarily add (or
remove) semicolons to make you feel better.
;;
2016-09-30 14:19 GMT+02:00 Kai Koehne :
> To make a proposal: Let’s use semicolons in imperative JS parts of QML in
> our examples and documentation.
>
> Apart from being on the safe side regarding some pathological cases, it
> also makes the difference between declarative QML bindings and
>
> im
I think that would be fine to require semicolons everywhere except last
statement (and if there is single statement in the binding, no semi-colons are
needed at all)
I'm fine with having no semicolon on single statement bindings or signal
handlers that also don't require a pair of curly bra
30.09.2016, 15:19, "Kai Koehne" :
> Hi,
>
> It’s Friday, so time for some bikeshedding ;)
>
> As you might know, the semicolon as a statement separator in JavaScript is
> optional. That is, most of the time you can just separate commands
>
> by newlines. There are a few pathological cases [1] th
Hi,
It’s Friday, so time for some bikeshedding ;)
As you might know, the semicolon as a statement separator in JavaScript is
optional. That is, most of the time you can just separate commands
by newlines. There are a few pathological cases [1] though where a semicolon is
needed. It seems the J
On 30/09/2016 11:57, Marc Mutz wrote:
On Friday 30 September 2016 12:39:20 Sean Harmer wrote:
Hi,
just a query as to how people do bulk checkouts of different branches
when working with the Qt git modules. It would be nice to be able to use
git submodule foreach ... but this is a problem beca
On 2016-09-30 11:39, Sean Harmer wrote:
Hi,
just a query as to how people do bulk checkouts of different branches
when working with the Qt git modules. It would be nice to be able to
use git submodule foreach ... but this is a problem because not all
modules use the same branching scheme.
So, w
On Friday 30 September 2016 12:39:20 Sean Harmer wrote:
> Hi,
>
> just a query as to how people do bulk checkouts of different branches
> when working with the Qt git modules. It would be nice to be able to use
> git submodule foreach ... but this is a problem because not all modules
> use the sam
Hi,
Without knowing the internals of COIN, is it a problem for CI load if we
request some WIP branches for upcoming major Qt 3D features? The
branches we would like are for features that will take many commits to
mature and involve many people so local branches are not enough and we
don't kno
Hi,
just a query as to how people do bulk checkouts of different branches
when working with the Qt git modules. It would be nice to be able to use
git submodule foreach ... but this is a problem because not all modules
use the same branching scheme.
So, what do people do to checkout all inte
Hi all,
Please test qt 5.8.0 beta snapshot
Windows: http://download.qt.io/snapshots/qt/5.8/5.8.0-beta/579/
Mac: http://download.qt.io/snapshots/qt/5.8/5.8.0-beta/446/
Src: http://download.qt.io/snapshots/qt/5.8/5.8.0-beta/latest_src/
Unfortunately we don't have working binary installers for
24 matches
Mail list logo
