Re: [Development] [OS X] green/welcome page disappears but widgets remain functional

2016-03-22 Thread René J . V . Bertin 
Kevin Funk wrote:

> The latter, yes. Just try.

Took me a while because I was upgrading to Qt 5.6.0.

Running
%> QT_LOGGING_RULES="*=true;qt.scenegraph*.debug=false" kdevelop5

Here's what I get when opening a 1st document over the welcome page:

kdevplatform.sublime: view added in Sublime::Area(0x7ff1128e42d0, name = "code")
kdevplatform.shell: added view in Sublime::Area(0x7ff1128e42d0, name = "code") 
, id "code_8168181"
kdevplatform.shell: recording change done to "code_8168181"
kdevplatform.shell: saving "code_8168181" from area
kdevplatform.shell: setting "code_8168181" persistent: false
kdevplatform.shell: loading working-set "code_8168181" into area 
Sublime::Area(0x7ff1128dbc60, name = "debug")
kdevplatform.shell: recycling 0 old views
kdevplatform.plugins.contextbrowser: new doc:  0x7ff114d5afb0  new cursor:  (0, 
0)
kdevplatform.plugins.contextbrowser: updating jump target
kdevplatform.plugins.contextbrowser: updating history
kdevplatform.plugins.contextbrowser: not updating box
kdevplatform.sublime: view added in Sublime::Area(0x7ff1128dbc60, name = 
"debug")
kdevplatform.shell: added view in Sublime::Area(0x7ff1128dbc60, name = "debug") 
, id "code_8168181"
kdevplatform.shell: doing nothing because loading
kdevplatform.shell: deleting  0  old views
kdevplatform.language: highlighting du chain 
QUrl("file:///Users/bertin/work/src/new/KDE/KF5/kded-git/CMakeLists.txt")
kdevplatform.language: highlighted 
QUrl("file:///Users/bertin/work/src/new/KDE/KF5/kded-git/CMakeLists.txt") in 
foreground
kdevplatform.language: Creating change tracker for  
QUrl("file:///Users/bertin/work/src/new/KDE/KF5/kded-git/CMakeLists.txt")
kdevplatform.language: Registered completion model
kdevplatform.plugins.documentswitcher: got signal from mainwindow: 
KDevelop::MainWindow(0x7ff1128f5790, name = "MainWindow") "5:KF5 projects:  
kded-git" its area is: Sublime::Area(0x7ff1128e42d0, name = "code") "Code" 
adding view: KDevelop::TextView(0x7ff110410df0) "CMakeLists.txt"
kdevplatform.shell: changing active view to KDevelop::TextView(0x7ff110410df0) 
doc KDevelop::TextDocument(0x7ff114d5af90, name = "CMakeLists.txt") mw 
KDevelop::MainWindow(0x7ff1128f5790, name = "MainWindow")
kdevplatform.shell: setting new XMLGUI client 
KTextEditor::ViewPrivate(0x7ff119357fc0)
kdevplatform.shell: Attempting to load "kdevastyle" - name: "AStyle Formatter 
Backend"
kdevplatform.shell: Successfully loaded plugin "kdevastyle" from 
"/opt/local/share/qt5/plugins/kdevplatform/25/kdevastyle.so" - took: 3 ms
kdevplatform.shell: add plugin AStylePlugin(0x7ff119531df0) "kdevastyle"
kdevplatform.shell: Attempting to load "kdevcustomscript" - name: "Custom 
Script Formatter Backend"
kdevplatform.shell: Successfully loaded plugin "kdevcustomscript" from 
"/opt/local/share/qt5/plugins/kdevplatform/25/kdevcustomscript.so" - took: 2 ms
kdevplatform.shell: add plugin CustomScriptPlugin(0x7ff1194a6af0) 
"kdevcustomscript"
kdevplatform.plugins.documentswitcher: moving view to front, list should now 
not contain this view anymore KDevelop::TextView(0x7ff110410df0) 
"CMakeLists.txt"
kdevplatform.plugins.documentswitcher: current area is: 
Sublime::Area(0x7ff1128e42d0, name = "code") "Code" mainwnidow: 
KDevelop::MainWindow(0x7ff1128f5790, name = "MainWindow") 
"file:///Users/bertin/work/src/new/KDE/KF5/kded-git/CMakeLists.txt"
kdevplatform.plugins.documentswitcher: idx of this view in list: -1
kdevplatform.plugins.contextbrowser: new doc:  0x7ff114d5afb0  new cursor:  (0, 
0)
kdevplatform.plugins.contextbrowser: updating jump target
kdevplatform.plugins.contextbrowser: updating history
kdevplatform.plugins.contextbrowser: not updating box
kdevplatform.plugins.contextbrowser: updating history
kdevplatform.plugins.contextbrowser: not updating box

Notice the "mainwnidow" ;)

Then, closing that document (take a deep breath):

kdevplatform.sublime: Closing view for 
"file:///Users/bertin/work/src/new/KDE/KF5/kded-git/CMakeLists.txt" views 3 in 
area Sublime::Area(0x7ff1128e42d0, name = "code")
kdevplatform.sublime: index  0x7ff112879cf0  root  0x7ff112879cf0
kdevplatform.sublime: splitter  QSplitter(0x7ff112c2cb50)  container  
Sublime::Container(0x7ff1150580d0)
kdevplatform.sublime: structure:  "CMakeLists.txt"  whole structure:  
"CMakeLists.txt"
kdevplatform.plugins.documentswitcher: removing view, list should now not 
contain this view anymore KDevelop::TextView(0x7ff110410df0) "CMakeLists.txt"
kdevplatform.plugins.documentswitcher: current area is: 
Sublime::Area(0x7ff1128e42d0, name = "code") "Code" mainwnidow: 
KDevelop::MainWindow(0x7ff1128f5790, name = "MainWindow") "5:KF5 projects:  
kded-git - [ kded-git:CMakeLists.txt ]"
kdevplatform.plugins.documentswitcher: idx of this view in list: -1
kdevplatform.shell: clearing last XML GUI client 
KTextEditor::ViewPrivate(0x7ff119357fc0)
kdevplatform.shell: removed view in Sublime::Area(0x7ff1128e42d0, name = 
"code") , id "code_8168181"
kdevplatform.shell: recording change done to "code_8168181"

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-22 Thread René J . V . Bertin 
René J.V. Bertin wrote:

Hi again,

> mOptions.testFlag(UseFreeTypeFontEngine)? 1.0 : 2.0

In fact, 0.95 may work even better than 1.0 .

R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 12:03:40 Marc Mutz wrote:
> On Tuesday 22 March 2016 11:20:44 Thiago Macieira wrote:
> > On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> > > This is a general issue in C++ and should be solved generally:
> > > 
> > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf
> > 
> > Do you know the status of this proposal? It's not in the latest language
> > draft available (N4567).
> 
> No, but I've asked on std-proposals now. Let's see.

https://cplusplus.github.io/EWG/ewg-active.html#76

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] QWidget and sizePolicy

2016-03-22 Thread Martin Koller 
In the docs I find:
"If there is a QLayout that manages this widget's children, the size policy 
specified by that layout is used. If there is no such QLayout, the result of 
this function is used."

However in the code I can not find a relation between the sizePolicy and a 
layout.
QWidget::sizePolicy() simply returns what it was given in 
QWidget::setSizePolicy()
A layout itself has no sizePolicy, so this also is strange.

Is this probably a leftover and the documentation was not updated or do I miss 
something ?

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Thiago Macieira 
On terça-feira, 22 de março de 2016 11:12:52 GMT Blasche Alexander wrote:
> The problem seem purely license related (other failures currently not
> visible). I would argue that we should fix integrations errors due to such
> issues.
> 
> I would favor another option though. We should disable the license check for
> modules which are ignored by .gitmodules.

How about disabling the CI completely and allowing direct staging like for Qt 
Creator and Qt 4.8?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Blasche Alexander 
The problem seem purely license related (other failures currently not visible). 
I would argue that we should fix integrations errors due to such issues.

I would favor another option though. We should disable the license check for 
modules which are ignored by .gitmodules.


--
Alex


From: Development 
 on 
behalf of Robin Burchell 
Sent: Tuesday, March 22, 2016 10:50
To: development@qt-project.org
Subject: Re: [Development] qtfeedback and qtdocgallery: status?

On Tue, Mar 22, 2016, at 10:37 AM, Hausmann Simon wrote:
> I'm not sure what you'd like me to answer at this point. I think that it
> is possible to fix the
> build of these modules, the CI system is in place for that. However it
> requires a fair bit of
> work (ask Robin about qtmessagingframework ;-).

Assuming that the problems are *just* limited to license tests, and the
tests in the package itself are in good shape, then it's probably not
*too* hard. It'll still require playing a few rounds of CI ping-pong,
and mass-staging changes (and headdesking when it fails again).

I'll readily admit that it's an annoying process, but it was a
manageable one. I'm not sure it's a productive use of time in the case
of these "smaller"/pseudo-abandonware codebases, but it's certainly
possible.

For the practicalities of how to do it (Simon or someone, please correct
me if I'm wrong here):

* You'll want to edit sync.profile in the module and make sure they
don't have "stale" dependencies (I see for instance that qtfeedback is
pointing to refs/heads/stable, which is probably not a good idea at this
point). I forget what the default is (no specific version listed) -- I
believe it points to the origin branch (e.g. 5.6 branch of module -> 5.6
of dependency), or dev if there's not a direct match.
* You can run the license test locally (from qtqa, see
./tests/prebuild/license/tst_licenses.pl) to check that it will be
satisfied with a given module

Robin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] C++11 initializer lists in Qt 5.7

2016-03-22 Thread Thiago Macieira 
On terça-feira, 22 de março de 2016 12:00:35 GMT Marc Mutz wrote:
> The same old problem:
> 
> std::_1::initializer_list vs. std:.initializer_list ? Or is 
> std::initializer_list one of those types (like std::exception) compatible 
> between libc++ and libstdc++?

Good question. The layout of std::initializer_list is mandated by the compiler 
ABI. But the actual type name does not necessarily have to be...

Checking libc++ sources...

8<-
namespace std  // purposefully not versioned
{

#ifndef _LIBCPP_HAS_NO_GENERALIZED_INITIALIZERS

template
class _LIBCPP_TYPE_VIS_ONLY initializer_list
8<-

There you go, the name is the same too (St16initializer_list). Very likely, 
this is required by the compilers themselves.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 11:20:44 Thiago Macieira wrote:
> On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> > This is a general issue in C++ and should be solved generally:
> > 
> > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf
> 
> Do you know the status of this proposal? It's not in the latest language
> draft available (N4567).

No, but I've asked on std-proposals now. Let's see.

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] C++11 initializer lists in Qt 5.7

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 11:33:57 Thiago Macieira wrote:
> [This is why I asked for an analysis of the features now possible, but it
> hasn't happened. So we're doing it piecemeal]
> 
> Sean wrote:
> > I don't have ready access to all the other compilers and versions we
> > support but I think this would allow potential use of:
> > 
> > * template aliases
> > * raw string literals
> > * delegating ctors
> 
> I'd written:
> > This buys us:
> > 
> > - delegating constructors
> > - "explicit operator" member funcvtions
> > - nsdmi
> > - initializer_list (not uniform initialisation!)
> > - raw strings
> > - template alias (using ... = ...)
> > - variadic templates
> 
> In specific for initializer_lists, the only compilers now with problems is
> M MSVC 2013 RTM and SP1. SP2 contains a fix that allows us to enable the
> functionality.
> 
> But since MSVC does not keep binary compatibility between versions, we
> should be allowed to use initializer_lists in our ABI.
> 
> Any disagreements?
> 
> cf https://codereview.qt-project.org/107373

The same old problem:

std::_1::initializer_list vs. std:.initializer_list ? Or is 
std::initializer_list one of those types (like std::exception) compatible 
between libc++ and libstdc++?

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] C++11 initializer lists in Qt 5.7

2016-03-22 Thread Thiago Macieira 
[This is why I asked for an analysis of the features now possible, but it 
hasn't happened. So we're doing it piecemeal]

Sean wrote:
> I don't have ready access to all the other compilers and versions we support
> but I think this would allow potential use of:
> 
> * template aliases
> * raw string literals
> * delegating ctors

I'd written:
> This buys us:
> 
> - delegating constructors
> - "explicit operator" member funcvtions
> - nsdmi
> - initializer_list (not uniform initialisation!)
> - raw strings
> - template alias (using ... = ...)
> - variadic templates

In specific for initializer_lists, the only compilers now with problems is M
MSVC 2013 RTM and SP1. SP2 contains a fix that allows us to enable the 
functionality.

But since MSVC does not keep binary compatibility between versions, we should 
be allowed to use initializer_lists in our ABI.

Any disagreements?

cf https://codereview.qt-project.org/107373
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-22 Thread Thiago Macieira 
On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> This is a general issue in C++ and should be solved generally:
> 
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf

Do you know the status of this proposal? It's not in the latest language draft 
available (N4567).

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Robin Burchell 
On Tue, Mar 22, 2016, at 10:37 AM, Hausmann Simon wrote:
> I'm not sure what you'd like me to answer at this point. I think that it
> is possible to fix the
> build of these modules, the CI system is in place for that. However it
> requires a fair bit of
> work (ask Robin about qtmessagingframework ;-).

Assuming that the problems are *just* limited to license tests, and the
tests in the package itself are in good shape, then it's probably not
*too* hard. It'll still require playing a few rounds of CI ping-pong,
and mass-staging changes (and headdesking when it fails again).

I'll readily admit that it's an annoying process, but it was a
manageable one. I'm not sure it's a productive use of time in the case
of these "smaller"/pseudo-abandonware codebases, but it's certainly
possible.

For the practicalities of how to do it (Simon or someone, please correct
me if I'm wrong here):

* You'll want to edit sync.profile in the module and make sure they
don't have "stale" dependencies (I see for instance that qtfeedback is
pointing to refs/heads/stable, which is probably not a good idea at this
point). I forget what the default is (no specific version listed) -- I
believe it points to the origin branch (e.g. 5.6 branch of module -> 5.6
of dependency), or dev if there's not a direct match.
* You can run the license test locally (from qtqa, see
./tests/prebuild/license/tst_licenses.pl) to check that it will be
satisfied with a given module

Robin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Hausmann Simon 

I'm not sure what you'd like me to answer at this point. I think that it is 
possible to fix the
build of these modules, the CI system is in place for that. However it requires 
a fair bit of
work (ask Robin about qtmessagingframework ;-).

However fixing the modules appears to me to be orthogonal to the question about 
whether
they should be mentioned in .gitmodules or not. It is my opinion that them 
being listed in
the file does not cause any harm because they have the status "ignore", which 
excludes them
from init-repository, the CI system and consequently the release of Qt.

Simon


From: Development 
 on behalf 
of Marc Mutz 
Sent: Tuesday, March 22, 2016 10:38
To: development@qt-project.org
Subject: Re: [Development] qtfeedback and qtdocgallery: status?

On Tuesday 22 March 2016 09:58:48 Hausmann Simon wrote:
> As the modules are not part of any release of Qt and unmaintained, I don't
> think they need fixing.

C'mon — FTBFS without the possibility to submit a fix?

--
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 09:58:48 Hausmann Simon wrote:
> As the modules are not part of any release of Qt and unmaintained, I don't
> think they need fixing.

C'mon — FTBFS without the possibility to submit a fix?

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Hausmann Simon 

As the modules are not part of any release of Qt and unmaintained, I don't 
think they need fixing.

Simon


From: m...@kdab.com  on behalf of Marc Mutz 
Sent: Tuesday, March 22, 2016 9:37
To: Hausmann Simon
Cc: development@qt-project.org
Subject: Re: [Development] qtfeedback and qtdocgallery: status?

On Tuesday 22 March 2016 09:19:26 Hausmann Simon wrote:
> Hi,
>
> I see no reason for dropping them from qt5.git as long as they are in
> status = ignore
> (http://code.qt.io/cgit/qt/qt5.git/tree/.gitmodules?h=5.6.0 ). What harm
> does it cause?

You mean other than failing integrations? None.

Specifically, I'l like to enable -Wzero-as-null-pointer-constant in headercheck
and those are the only modules that have not integrated the respective fixes.

What about the other option, then? Fixing them? I have no idea how to fix them
so that both 5.6 and 5.7 are happy, and they don't follow the Qt branching, it
seems.

Thanks,
Marc

--
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 09:19:26 Hausmann Simon wrote:
> Hi,
> 
> I see no reason for dropping them from qt5.git as long as they are in
> status = ignore
> (http://code.qt.io/cgit/qt/qt5.git/tree/.gitmodules?h=5.6.0 ). What harm
> does it cause?

You mean other than failing integrations? None.

Specifically, I'l like to enable -Wzero-as-null-pointer-constant in headercheck 
and those are the only modules that have not integrated the respective fixes.

What about the other option, then? Fixing them? I have no idea how to fix them 
so that both 5.6 and 5.7 are happy, and they don't follow the Qt branching, it 
seems.

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] qtfeedback and qtdocgallery: status?

2016-03-22 Thread Marc Mutz 
Hi,

what, exactly, is the status of the QtFeedback and QtDocGallery modules? They 
are submodules of qt5/5.6, but they accept no integrations due to the license 
header check failing, cf.

   https://codereview.qt-project.org/151189 (qtfeedback)
   https://codereview.qt-project.org/151253 (qtdocgallery)

Can we either fix these modules so integrations succeed again, or else drop 
them from the list of submodules, please?

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] http://testresults.qt.io/ci/status/ stale?

2016-03-22 Thread Hausmann Simon 
Not implemented feature. That site is a mirror of the internal system and we do 
not mirror running integrations currently.


Simon

  Original Message
From: Marc Mutz
Sent: Tuesday, March 22, 2016 08:50
To: development@qt-project.org
Subject: Re: [Development] http://testresults.qt.io/ci/status/ stale?


On Tuesday 22 March 2016 07:32:45 Liang Qi wrote:
> The status of new CI: http://testresults.qt.io/coin/

About that: it always shows "no integrations running", while clearly there are
active integrations according to Gerrit. Bug or feature?

Thanks,
Marc

--
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] http://testresults.qt.io/ci/status/ stale?

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 07:32:45 Liang Qi wrote:
> The status of new CI: http://testresults.qt.io/coin/

About that: it always shows "no integrations running", while clearly there are 
active integrations according to Gerrit. Bug or feature?

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] http://testresults.qt.io/ci/status/ stale?

2016-03-22 Thread Liang Qi 
The status of new CI: http://testresults.qt.io/coin/

On 21 March 2016 at 18:19, MrMstormo .  wrote:

>
> Looks like
> http://testresults.qt.io/ci/status/
> is stale? All reports are erroring out, and there's no reports for 5.6,
> 5.7 etc?
>
> Is the CI system on an early Easter break? :)
>
> --
> .marius
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
http://www.qiliang.net
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-22 Thread Marc Mutz 
On Tuesday 22 March 2016 03:01:44 Stephen Kelly wrote:
> Thiago Macieira wrote:
> > On sábado, 19 de março de 2016 19:02:08 GMT Stephen Kelly wrote:
> >> Hi,
> >> 
> >> 
> >> 
> >> In case you missed it, I wrote an auto-modernizer
> >> 
> >>  https://steveire.wordpress.com/2016/03/19/aaargh
> >> 
> >> It is not quite AAA, as it doesn't convert
> >> 
> >>  QString s;
> >> 
> >> into
> >> 
> >>  auto s = QString();
> > 
> > Thanks Stephen
> > 
> > 
> > 
> > The post is very informative. Thanks for the tool too.
> 
> Great, thanks!
> 
> > But if the code above were auto, s would be a QStringArgBuilder. And if
> > 
> > you had later:
> > 
> > 
> > 
> > someFunction(s.arg(M_PI));
> > 
> > 
> > 
> > We'd have a behaviour change...
> 
> Note that this is nothing to do with the tool, so I've broken out a
> different thread.
> 
> 3rd party code is already using
> 
> auto s = tr("%1 (%2)").arg(someString()).arg(42);
> 
> someFunction(s.arg(M_PI));
> 
> so your proposal is not as source compatible as you think.
> 
> It is about as source compatible as QStringBuilder is when introduced to
> code which already uses auto. QStringBuilder is not on-by-default for
> operator+, or wasn't the last I checked, so a user could enable it today
> for a codebase which already uses auto extensively with a result of
> strange runtime behavior.
> 
> Presumably your proposal is either Qt6 material or something to be
> enabled by the user with a compile definition similar to QStringBuilder.
> Problems like you describe could similarly be found with a clazy check.

This is a general issue in C++ and should be solved generally:

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf

Thanks,
Marc

-- 
Marc Mutz  | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development