Re: [Development] QZipReader and QZipWriter

From: development-bounces+tero.kojo=digia@qt-project.org [mailto:development-bounces+tero.kojo=digia@qt-project.org] On Behalf Of Gunnar Roth Sent: 4. elokuuta 2014 9:37 To: development@qt-project.org Subject: Re: [Development] QZipReader and QZipWriter Hi, sorry my comment has no rela

Re: [Development] Merging Qt 5.3 branch into dev branch

Hi Frederik, Pretty please with sugar on top, do a merge quicker. My patches add new features to Qt 5.4 and there are just a few days until feature freeze. Cheers, BogDan. Hi, On Monday, August 04, 2014 07:23:46 AM BogDan wrote: > Hello, > > Is there any chance to have a more often merging

Re: [Development] Problem compiling qtcreator on armhf

JFTR this has been tracked until the combination of -g and -O2. The full bug log is available at [0] and [1]. [0] [1] -- May the source be with you. Lisandro Damián Nicanor Pérez Meyer htt

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 2014-08-04, at 03:38 PM, Adam Strzelecki wrote: >> Before you do that, can you write up a proposal on what you want to >> accomplish and how to get there? > > WHAT I WANT TO ACOMPLISH > > (1) Remove need to rewrite Qt libraries (frameworks) headers during install > and during macdeployqt >

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 2014-08-04, at 08:22 AM, Thiago Macieira wrote: > On Monday 04 August 2014 12:22:01 Adam Strzelecki wrote: >> I have wrote that your suggestions should be implemented without any doubt, >> but whether copy on build should be default it is really a matter of >> preference, that's why this has t

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

> Before you do that, can you write up a proposal on what you want to > accomplish and how to get there? WHAT I WANT TO ACOMPLISH (1) Remove need to rewrite Qt libraries (frameworks) headers during install and during macdeployqt (2) This makes possible to check whether libraries came from offic

Re: [Development] Merging Qt 5.3 branch into dev branch

Hi, On Monday, August 04, 2014 07:23:46 AM BogDan wrote: > Hello, > > Is there any chance to have a more often merging of 5.3 branch into dev? > I have a few pending patches for dev branch which depends on others that I > pushed to 5.3 branch a few days ago. I usually try to do a merge roughly e

[Development] Merging Qt 5.3 branch into dev branch

Hello, Is there any chance to have a more often merging of 5.3 branch into dev? I have a few pending patches for dev branch which depends on others that I pushed to 5.3 branch a few days ago. Cheers, BogDan. ___ Development mailing list Development@qt-

[Development] QJsonDocument parsing file size limit

Hello, Please correct me if this is not the correct place to post this question. I am wondering why the file size limit to parse JSON files with QJsonDocument::parse(..) is around 128MB? Are there plans to increase this limit in future releases? Cheers, Jose _

Re: [Development] [docs/c++] How do we deal with the special member functions (copy/move ctor/assignment operator, dtor, default ctor)

On 04/08/14 14:27, "Thiago Macieira" wrote: >On Monday 04 August 2014 09:31:12 Marc Mutz wrote: >> On Monday 04 August 2014 08:02:51 Knoll Lars wrote: >> > On 02/08/14 18:21, "Thiago Macieira" >>wrote: >> > >Why do we have to document them in the first place? I hate having to >> > >write >> > >d

Re: [Development] [docs/c++] How do we deal with the special member functions (copy/move ctor/assignment operator, dtor, default ctor)

On Monday 04 August 2014 09:31:12 Marc Mutz wrote: > On Monday 04 August 2014 08:02:51 Knoll Lars wrote: > > On 02/08/14 18:21, "Thiago Macieira" wrote: > > >Why do we have to document them in the first place? I hate having to > > >write > > >documentation for a destructor that simply says "frees

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On Monday 04 August 2014 12:22:01 Adam Strzelecki wrote: > I have wrote that your suggestions should be implemented without any doubt, > but whether copy on build should be default it is really a matter of > preference, that's why this has to be config option which may be default or > not, I don't

Re: [Development] Relative paths in EXAMPLE_FILES in .pro files

On Monday 04 August 2014 08:57:25 Sumedha Widyadharma wrote: > See: mkspecs/features/qt_example_installs.prf > > > You can assign any value to any variable you want in qmake. Whether you > > make use of the variable or not, it's up to you. > > This variable is used internally. You mean "external

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 04 Aug 2014, at 12:22, Adam Strzelecki wrote: >> So, let's end this discussion and start focusing efforts towards building >> the solution. > > > Now let's focus on submitting patches :> Before you do that, can you write up a proposal on what you want to accomplish and how to get there? T

Re: [Development] Problem compiling qtcreator on armhf

On Saturday 02 of August 2014 14:53:10 Lisandro Damián Nicanor Pérez Meyer wrote: > Just for the record, I'm also seeing this while compiling: > > /home/lisandro/qtcreator/src/plugins/qmldesigner/designercore/model/qmltextg > enerator.cpp: In member function 'QString > QmlDesigner::Internal::Qml

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

> So, let's end this discussion and start focusing efforts towards building the > solution. I have wrote that your suggestions should be implemented without any doubt, but whether copy on build should be default it is really a matter of preference, that's why this has to be config option which

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On Fri, Aug 01, 2014 at 02:24:03PM -0400, Jake Petroules wrote: > What might be good, too, is a QMAKE_EMBEDDED_FRAMEWORKS or somesuch > which copies the Qt frameworks into the application bundle at build > time (though you'd still set DYLD_LIBRARY_PATH because not everyone > would necessarily use Q

Re: [Development] Relative paths in EXAMPLE_FILES in .pro files

On Fri, Aug 01, 2014 at 04:45:16PM +0200, Sumedha Widyadharma wrote: > It is silently dropped, you have to enable CONFIG+=check_examples to > get a notice about this. Why is that? > > Shouldn't it always warn the user? > there are some false positives which i found non-trivial to avoid cleanly, s

Re: [Development] QZipReader and QZipWriter

On Mon, Aug 04, 2014 at 08:36:37AM +0200, Gunnar Roth wrote: > sorry my comment has no relation to KArchive in special, I appreciate > [y]our efforts. I was the attitude which let me maybe overreact. We > could as well switch to LGPL and save a lot of money. > this is the _contributor_ _community

Re: [Development] My availability

Hi Stephen, Thanks for the reviewing and help ! Since you'll have less time, will you keep the Model/View maintainer role ? On 16 juil. 2014, at 15:49, Robert Knight wrote: > Hi Stephen, > > Thanks for all your contributions over the years. Up to anything > interesting next? > > On 16 July 2

Re: [Development] [docs/c++] How do we deal with the special member functions (copy/move ctor/assignment operator, dtor, default ctor)

On Monday 04 August 2014 08:02:51 Knoll Lars wrote: > On 02/08/14 18:21, "Thiago Macieira" wrote: > >On Friday 01 August 2014 23:16:40 Marc Mutz wrote: > >> That leaves the question how to deal with the documentation for these > >> implicit members. > > > >Why do we have to document them in the f