Oswald Buddenhagen wrote:
> On Fri, Mar 18, 2016 at 12:54:25PM +0100, René J. V. Bertin wrote:
>> Is that correct? Trying this currently fails because at some point headers
>> are not found that are expected in a QtWebkit framework:
>>
> that means that the packagers failed to run syncqt.
So, b
Il 16/03/2016 16:14, Koehne Kai ha scritto:
We already have the coding conventions
page:https://wiki.qt.io/Coding_Conventions . But we haven't done a good job at
keeping it up to date - and one reason is IMO that, given that it's a wiki
everybody can edit, people in a twist of irony stay away
Am Freitag, 18. März 2016, 10:26:14 CET schrieb Marc Mutz:
> Hi,
>
> Compiler upgraded in the CI without checking Qt compiles with it first? :)
>
> Fix: https://codereview.qt-project.org/153309
I think the error is caused by your patch "QtWidgets: includemocs"
clang can only warns about this k
On Friday 18 March 2016 10:26:14 Marc Mutz wrote:
> Hi,
>
> Compiler upgraded in the CI without checking Qt compiles with it first? :)
Sorry for accusing the CI team. It turns out to be cause by one of my patches.
It's triggered by running includemocs in src/widgets. Clang now sees all the
func
+1
Il 16/mar/2016 16:14, "Koehne Kai" ha scritto:
> Hi there,
>
> We have had quite some discussions about the use of C++11 features and
> right API in the past on this mailing list - but if there has been a
> consensus (which is sometimes hard to find out), it was often buried pretty
> deep in t
Hi,
Just wanted to let you all know that Qt 5.6 has been released today. For
details, check out http://www.qt.io/qt5-6/ and the blog post at
http://blog.qt.io/blog/2016/03/16/qt-5-6-released/ .
Cheers,
Lars
___
Announce mailing list
annou...@qt-proj
(snip)
On Friday, March 18, 2016 08:48:52 AM Jedrzej Nowacki wrote:
> So I think, that we should not discuss what is better qdoc or md. The real
> discussion is about tooling, what is the best tool to sanitize Qt code.
This thread is derailing.
Kai wants to move a few wiki documents to git, ther
> On 18 Mar 2016, at 08:48, Jędrzej Nowacki
> wrote:
>
> So I think, that we should not discuss what is better qdoc or md. The real
> discussion is about tooling, what is the best tool to sanitize Qt code. We
> need something that:
> 1. Can work as a sanity bot
> 2. Can re-format the code by
On Friday 18 March 2016 17:05:37 Knoll Lars wrote:
> On 18/03/16 16:03, "Development on behalf of Marc Mutz" wrote:
> >On Friday 18 March 2016 15:37:40 André Somers wrote:
> >> Op 18/03/2016 om 09:24 schreef Rutledge Shawn:
> >> > Forcing it on everyone that way will be controversial, because ther
In working with QChart (which overall I LOVE btw) I have hit some issues..
First, I would love to see/learn the proper way to reload a chart. If I have a
chart with a data, but due to user option to set what data is shown, and the
user changes an option, I need to recompute the data and then r
Heikkinen Jani wrote:
> Hi!
>
> Webkit packages can be found from here:
> http://download.qt.io/community_releases/5.6/5.6.0/
Indeed, thanks!
R.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/deve
I have Xcode 7.2.1 and OSX 10.11.3 installed, but my Xcode isn't allowing me to
compile qdoc. The compiler says it can't find things like #include ,
which means it isn't installed correctly. But I have no idea what's wrong.
martin
From: Development
on behalf
> -Original Message-
> From: Development [mailto:development-
> [...]
> It remains that this document is expected to be quite stable, so there would
> be some sense to having a stable URL to which we routinely copy the new
> version once a change to the source has been accepted. The effo
Giuseppe D'Angelo:
>>> The question is, can/should we get the HTML output of these documents
>>> published somewhere, for ease of access?
All the HTML generated from QDoc in all of our code should be visible in
some public way. This would just be one more page of that.
>>> Do they need their own
On Friday 18 March 2016 23:45:22 Marc Mutz wrote:
> On Friday 18 March 2016 17:05:37 Knoll Lars wrote:
> > On 18/03/16 16:03, "Development on behalf of Marc Mutz"
> bounces+lars.knoll=theqtcompany@qt-project.org on behalf of
>
> marc.m...@kdab.com> wrote:
> > >On Friday 18 March 2016 15:37:4
On 18 Mar 2016, at 08:48, Jędrzej Nowacki
mailto:jedrzej.nowa...@theqtcompany.com>>
wrote:
Every time someone discuss coding style issues my blood boils. I understand
that it is important to have consistent coding style, but discussing where to
put braces or spaces is just waste of developing t
16 matches
Mail list logo