Re: [Development] Imageformats v2

2015-05-20 Thread Rutledge Shawn
On 19 May 2015, at 21:00, Konstantin Ritt wrote: > IIUC, this already covered by the idea: since we can not (currently?) support > animated "pages", we treat both a multi-page tiff and an animated gif as a > document with N "frames”. I thought so. > > What you described sounds more like mip

Re: [Development] Compiling for iOS, qtdeclarative and others fail

2015-05-20 Thread Harri Pasanen
It's been a while since I compiled for iOS, but I recall having to run in the terminal on the build machine itself. Compiling over ssh did not work because of some signing issue, keystore access or some such was not available in ssh shell. I'm not sure if you have the same issue or not. Just

Re: [Development] Suggested addition to wiki.qt.io/Coding_Conventions

2015-05-20 Thread Thiago Macieira
On Tuesday 19 May 2015 11:47:47 Marc Mutz wrote: > Taking this train of thought one stop further: this is also makes QString > BiC: > > class Q_CORE_EXPORT QString > { > public: > // ... > #ifdef Q_COMPILER_RVALUE_REFS > inline QString(QString && other) Q_DECL_NOTHROW : d(other.d) >

Re: [Development] Compiling for iOS, qtdeclarative and others fail

2015-05-20 Thread Edward Sutton
On May 20, 2015, at 12:55 PM, Ariel Molina mailto:ar...@edis.mx>> wrote: >To be exactly, it compiles with make, but sudo make install fails. We are in “the same boat” then. That is the same issue I have building and installing Qt 5.5 iOS. New Qt 5.5 snapshots are available if that may help:

Re: [Development] Suggested addition to wiki.qt.io/Coding_Conventions

2015-05-20 Thread Olivier Goffart
On Tuesday 19. May 2015 11:47:47 Marc Mutz wrote: > Taking this train of thought one stop further: this is also makes QString > BiC: > > class Q_CORE_EXPORT QString > { > public: > // ... > #ifdef Q_COMPILER_RVALUE_REFS > inline QString(QString && other) Q_DECL_NOTHROW : d(other.d)

Re: [Development] Compiling for iOS, qtdeclarative and others fail

2015-05-20 Thread Ariel Molina
To be exactly, it compiles with make, but *sudo make install* fails. On Wed, May 20, 2015 at 11:54 AM, Ariel Molina wrote: > I was tracking a bug in Qt for desktop, then tried to test it on iOS but i > cant build Qt 5 for iOS. > > I have a valid Apple Account, paid for the license and I can buil

Re: [Development] [Interest] Imageformats v2

2015-05-20 Thread Konstantin Ritt
2015-05-20 19:27 GMT+04:00 Иван Комиссаров : > > > 2015-05-20 15:18 GMT+03:00 André Somers : >> >> I think that it makes sense to attempt to load a header if it exists. >> If not... Not sure. Probably need to read the entire file in order to >> determine what it contains? >> > > Any other opinion

Re: [Development] Compiling for iOS, qtdeclarative and others fail

2015-05-20 Thread Edward Sutton
I understand the config commands used to build Qt packages are here: http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config Qt iOS Enterprise: http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config/configure_ios_enterprise -commercial -confirm-license -debug-and

[Development] Compiling for iOS, qtdeclarative and others fail

2015-05-20 Thread Ariel Molina
I was tracking a bug in Qt for desktop, then tried to test it on iOS but i cant build Qt 5 for iOS. I have a valid Apple Account, paid for the license and I can build XCode and Qt apps for iPad, it works, but not Qt itself, here's my procedure 1. Git clone qt5 2. perl init-repository 3.

Re: [Development] Suggested addition to wiki.qt.io/Coding_Conventions

2015-05-20 Thread Marc Mutz
On Saturday 16 May 2015 22:01:36 Marc Mutz wrote: > On Wednesday 13 May 2015 09:30:05 Thiago Macieira wrote: > > The drawbacks only appear in debug builds, so is this worth the > > uglification? > > Yet another example of things that go wrong when blindly exporting > classes wholesale: > > http:

Re: [Development] [Interest] Imageformats v2

2015-05-20 Thread Иван Комиссаров
2015-05-20 15:18 GMT+03:00 André Somers : > > Problem is that you cannot show your _own_ message anymore. I might > want to choose a different wording in a message that I'd like to show to my > end user than something a Qt engineer choose. I also might like to offer > different choices for differ

[Development] Fwd: [Interest] Imageformats v2

2015-05-20 Thread Иван Комиссаров
btw, wrong list again:( -- Forwarded message -- From: Иван Комиссаров Date: 2015-05-20 14:36 GMT+03:00 Subject: Re: [Interest] [Development] Imageformats v2 To: André Somers Cc: "inter...@qt-project.org" 2015-05-20 13:19 GMT+03:00 André Somers : > Иван Комиссаров schreef op

Re: [Development] Binary compatibility for qtestlib

2015-05-20 Thread Thiago Macieira
On Wednesday 20 May 2015 11:28:26 Knoll Lars wrote: > >So do we maintain binary compatibility for testlib‎? > > I don’t see a strong use case for staying binary compatible with testlib. There is one use-case, which is to run regression tests without recompiling the unit test. All the tests that

Re: [Development] Binary compatibility for qtestlib

2015-05-20 Thread Hausmann Simon
Okay, thanks - that sounds good to me. The change in particular that I was thinking of is ‎https://codereview.qt-project.org/#/c/112690/ It could be done without breaking BC but it's easier if we can :) Simon From: Jason McDonald Sent: Wednesday, May 20, 2015 13:27 To: Hausmann Simon Cc: deve

Re: [Development] Fwd: Imageformats v2

2015-05-20 Thread André Somers
Иван Комиссаров schreef op 20-5-2015 om 12:45: > Hm, i pressed wrong button when replying to the letter:) As did I. I intended for it to be send to the list. Have done that now. André ___ Development mailing list Development@qt-project.org http://lists

Re: [Development] Binary compatibility for qtestlib

2015-05-20 Thread Knoll Lars
On 20/05/15 13:16, "Hausmann Simon" wrote: >‎Hi, > > >Lately development of testlib picked up again and I've been wondering: >the api consists of a fair amount of macros that call "internal" >functions. It would be convenient to change the signature > of those while maintaining source compatibil

Re: [Development] Binary compatibility for qtestlib

2015-05-20 Thread Jason McDonald
On Wed, May 20, 2015 at 9:16 PM, Hausmann Simon < simon.hausm...@theqtcompany.com> wrote: > ‎Hi, > > Lately development of testlib picked up again and I've been wondering: > the api consists of a fair amount of macros that call "internal" functions. > It would be convenient to change the signatu

[Development] Binary compatibility for qtestlib

2015-05-20 Thread Hausmann Simon
‎Hi, Lately development of testlib picked up again and I've been wondering: the api consists of a fair amount of macros that call "internal" functions. It would be convenient to change the signature of those while maintaining source compatibility, however it would naturally break the ABI. On t

[Development] Fwd: Imageformats v2

2015-05-20 Thread Иван Комиссаров
Hm, i pressed wrong button when replying to the letter:) -- Forwarded message -- From: Иван Комиссаров Date: 2015-05-20 12:06 GMT+03:00 Subject: Re: [Development] Imageformats v2 To: André Somers 2015-05-20 10:05 GMT+03:00 André Somers : > Иван Комиссаров schreef op 19-5-20

[Development] Fwd: Imageformats v2

2015-05-20 Thread Иван Комиссаров
-- Forwarded message -- From: André Somers Date: 2015-05-20 13:19 GMT+03:00 Subject: Re: [Development] Imageformats v2 To: Иван Комиссаров Иван Комиссаров schreef op 20-5-2015 om 11:06: 2015-05-20 10:05 GMT+03:00 André Somers : > Иван Комиссаров schreef op 19-5-2015 om 19:

[Development] New Qt 5.5 snapshot available

2015-05-20 Thread Heikkinen Jani
Hi all, New Qt 5.5 snapshot available windows: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-19_62/ linux: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-20_89/ mac: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-19_74/ If you have some pending changes for Qt5

Re: [Development] Imageformats v2

2015-05-20 Thread André Somers
Иван Комиссаров schreef op 19-5-2015 om 19:43: Let me describe current API and the ideas behind it. The core class is the ImageDocument - this is the replacement of the QImageReader/QImageWriter. Reader and writer has similar API and implemented in the same way, so i’ve decided to merge them i