Re: [Development] RCC XML and options

2014-09-04 Thread Thiago Macieira
On Thursday 04 September 2014 20:03:24 André Pönitz wrote: > > That is, I’m adding logic to run rcc over a *.qrc file to produce > > a cpp file. > > > > First, I read about the -compress / -no-compress options. That is all or > > nothing for the entire translation unit. Is there an attribute in th

Re: [Development] RCC XML and options

2014-09-04 Thread André Pönitz
On Thu, Sep 04, 2014 at 06:46:04PM +, John M. Dlugosz wrote: > > On 9/4/2014 1:03 PM, André Pönitz apoenitz-at-t-online.de |Qt Dev mailing > list/Qt| wrote: > > [Out of curiosity, what are the "standard platform tools" in this case?] > MSBuild. Runs from automated build server, testing serv

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

2014-09-04 Thread Thiago Macieira
On Thursday 04 September 2014 20:31:49 Andre Somers wrote: > That sounds rather short-sighted to me. > It means that an inconsistency is introduced for no good reason at all. > If you want to have something that works for English only, it would be > rather trivial to write a free function like this

Re: [Development] RCC XML and options

2014-09-04 Thread John M. Dlugosz
On 9/4/2014 1:03 PM, André Pönitz apoenitz-at-t-online.de |Qt Dev mailing list/Qt| wrote: > [Out of curiosity, what are the "standard platform tools" in this case?] MSBuild. Runs from automated build server, testing server, as well as in the desktop IDE. >> Let me make sure I understand what t

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

2014-09-04 Thread Andre Somers
On 4-9-2014 18:26, Thiago Macieira wrote: > On Thursday 04 September 2014 13:03:12 Saether Jan-Arve wrote: >> Somebody already suggested to embed it as a resource, isn't that good >> enough? > As long as we also load it by default. We cannot depend on users loading the > translation file from the r

Re: [Development] RCC XML and options

2014-09-04 Thread André Pönitz
On Thu, Sep 04, 2014 at 01:19:52PM +, John M. Dlugosz wrote: > I read the documentation on the Resource Compiler (rcc), and my interest > is in building existing projects using standard platform tools without > qmake. [Out of curiosity, what are the "standard platform tools" in this case?] >

Re: [Development] iOS Qt 5.3 CI broken

2014-09-04 Thread Jake Petroules
On 2014-09-04, at 03:34 AM, Knoll Lars wrote: > > > On 04/09/14 03:19, "Jake Petroules" wrote: > >> On 2014-09-03, at 07:58 PM, Thiago Macieira >> wrote: >> >>> Could someone either fix it or disable iOS builds in the CI for 5.3? >>> >>> >>> /Applications/Xcode.app/Contents/Developer/Tool

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

2014-09-04 Thread Thiago Macieira
On Thursday 04 September 2014 13:03:12 Saether Jan-Arve wrote: > Somebody already suggested to embed it as a resource, isn't that good > enough? As long as we also load it by default. We cannot depend on users loading the translation file from the resource system. > > Imagine an application that

[Development] DockAreaWidget and QGLWidget update / repaint / paintEvent

2014-09-04 Thread Renaud
Hi All, I'm working on porting huge applications from Qt4(.7.2) to Qt5.(3.0). The applications use massively QGLWidget (and openGL). On Qt4, it works perfectly. On Qt5, I got some issues: 1/The applications have many mechanisms which start from MouseMoveEvent to updateGL() the QGLWidget (select

[Development] RCC XML and options

2014-09-04 Thread John M. Dlugosz
I posted this on the Qt forum, but it was suggested that I bring it to the mailing list instead. The original post is at http://qt-project.org/forums/viewthread/46927 I read the documentation on the Resource Compiler (rcc), and my interest is in building existing projects using standard platfo

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

2014-09-04 Thread Saether Jan-Arve
> -Original Message- > From: development-bounces+jan-arve.saether=digia@qt-project.org > [mailto:development-bounces+jan-arve.saether=digia@qt-project.org] > On Behalf Of Thiago Macieira > Sent: 3. september 2014 18:11 > To: development@qt-project.org > Subject: Re: [Development]

[Development] QTCREATORBUG-11516 and QTBUG-37119

2014-09-04 Thread Helmut Mülner
For several months now it is not possible to evaluate Javascript expressions in the QML-Debugger component of QtCreator, so we are back to console.log() debugging. This issue was reported end of February and has a P2 priority. But it looks like there is no progress in this case. Could somebod

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-04 Thread Richard Moore
On 4 September 2014 10:29, Allan Sandfeld Jensen wrote: > On Thursday 04 September 2014, Richard Moore wrote: > > On 3 September 2014 20:25, Thiago Macieira > > > > wrote: > > > > > How is it represented in HTML5? > > > > > Just do it the same way. > > > > > > > > I'm a little unsure that I unde

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-04 Thread Allan Sandfeld Jensen
On Thursday 04 September 2014, Richard Moore wrote: > On 3 September 2014 20:25, Thiago Macieira > > wrote: > > > > How is it represented in HTML5? > > > > Just do it the same way. > > > > > > I'm a little unsure that I understood. Could you please clarify what > > > did you mean by "represented

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-04 Thread Richard Moore
On 3 September 2014 20:25, Thiago Macieira wrote: > > > How is it represented in HTML5? > > > Just do it the same way. > > > > I'm a little unsure that I understood. Could you please clarify what did > > you mean by "represented in HTML5"? > > XMLHttpRequests have existed in JavaScript and HTML5

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

2014-09-04 Thread Knoll Lars
On 04/09/14 07:54, "Thiago Macieira" wrote: >On Thursday 04 September 2014 05:24:38 Rutledge Shawn wrote: >> It doesn't necessarily occur to an English speaker to identify >>translatable >> strings and wrap them in tr(), either. It is some work already to try >>to >> support localization, so we

Re: [Development] iOS Qt 5.3 CI broken

2014-09-04 Thread Knoll Lars
On 04/09/14 03:19, "Jake Petroules" wrote: >On 2014-09-03, at 07:58 PM, Thiago Macieira >wrote: > >> Could someone either fix it or disable iOS builds in the CI for 5.3? >> >> >>/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctool >>chain/usr/bin/clang >> -c -pipe -fvis