Re: [Development] Perf about loading one 240x320 png image

On Sat, Sep 29, 2012 at 05:21:47AM +, song.7@nokia.com wrote: > Hi, > from resource > > from file system > It seems the performance is really bad,,, does anyone have some insight about > which place can be the bottleneck ? is this on a linux system? Use perf record -g on your testcase

[Development] Perf about loading one 240x320 png image

Hi, I am testing the image loading performance in Qt5, that the image with different location (qt resource or file system) and using QImage or QPixmap. Testing is based on a low end devices, and the result is shared as bellow: Loading perf (240x320 png image) from resource from file system Q

Re: [Development] Really bad graphics view text rendering in Qt 5 on Mac

On 9/28/12 4:03 PM, Stephen Chu wrote: > Just reported this bug: > > > Regardless of currently scaling factor, QGraphicsTextItem seems to be > rendered onto a back buffer with the same resolution as the screen > before copied onto the painting

[Development] Really bad graphics view text rendering in Qt 5 on Mac

Just reported this bug: Regardless of currently scaling factor, QGraphicsTextItem seems to be rendered onto a back buffer with the same resolution as the screen before copied onto the painting surface. __

Re: [Development] Co-installation & library naming rules

On Fri 28 Sep 2012 09:06:43 Sune Vuorela escribió: [snip] > I don't have any opinion on if we want to make it libQt5Stuff or > libQtStuff5. IMVHO, libQt5Stuff seems cleaner. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Descript

Re: [Development] Making Qt docs links on nokia.com 'cool'

Hi, We can have a look if stg can be done. It seems that redirecting fails, even though same page does exist. Yours, -- Tuukka Stephen Kelly kirjoitti 28.9.2012 18:35: Hi there, Cool Urls never change. http://www.w3.org/Provider/Style/URI Until the Qt handover, urls like h

[Development] Making Qt docs links on nokia.com 'cool'

Hi there, Cool Urls never change. http://www.w3.org/Provider/Style/URI Until the Qt handover, urls like http://qt.nokia.com/doc/latest/%1 such as http://qt.nokia.com/doc/latest/internationalization.html used to bring me to the Qt documentation. Now it brings me to the qt.digia.com site (n

Re: [Development] Branching for Qt 5 repositories

FWIW, +1. Ben - Original Message - > From: Hausmann Simon > To: Thiago Macieira ; "development@qt-project.org" > > Cc: > Sent: Friday, September 28, 2012 4:22 AM > Subject: Re: [Development] Branching for Qt 5 repositories > > > Sounds great, especially the branch names. +1 > >

Re: [Development] Co-installation & library naming rules

Stephen Kelly wrote: > On Friday, September 28, 2012 13:25:42 Thiago Macieira wrote: >> I've already contacted several downstreams: Sune for Debian, Will for >> OpenSUSE, Raphael for FreeBSD; the Fedora people were the originators of >> the bug report and have posted here. >> >> All have given th

Re: [Development] Qt5 Beta cross compiling problem

> Their is a naming convention for mkspecs ... not sure how it's definition > looks > exactly, but it should be named: linux-imx6-g++ My mkspec was in a folder "linux-imx6". I always thought the mkspec-folder was specified by the "-xplatform"-option in the configure-command? Now, I simply changed

Re: [Development] Qt5 Beta cross compiling problem

On sexta-feira, 28 de setembro de 2012 06.04.14, Thomas Senyk wrote: > I'm not sure I get what you trying to tell me :) > > Is it "You should change now, but if you're lucky you could get away with > beeing "lazy" and wait until ossi's changed settled and change then > accordingly"? > > ... because

Re: [Development] Qt5 Beta cross compiling problem

On Fri, September 28, 2012 01:30:34 PM Thiago Macieira wrote: > On sexta-feira, 28 de setembro de 2012 11.16.42, Thomas Senyk wrote: > > > No, it shouldn't. It should be linux-g++-imx6. There are several > > > sections > > > of the .pro files that test for "--*", e.g. in simd.prf: > > > > > > *-g+

Re: [Development] Qt5 Beta cross compiling problem

One side note, as I just stumbled over it: I need to pass: -no-pch to configure See: http://qt-project.org/forums/viewthread/20202 On Thu, September 27, 2012 05:11:23 PM Christoph Kurz wrote: > Hi, > > I have a problem cross compiling the Qt5-Beta for an i.MX6 Board. > The host OS is a Fedora Li

Re: [Development] Branching for Qt 5 repositories

"stable" and "release" are too similar in meaning and might cause confusion. Debian's naming scheme: unstable(or dev is fine)/testing/stable is easier to understand at a glance. KISS Keeping the word "master" out is a good idea though... since it's what git defaults to and doesn't really tell you

Re: [Development] Co-installation & library naming rules

On 2012-09-28, Stephen Kelly wrote: > On Friday, September 28, 2012 13:25:42 Thiago Macieira wrote: >> I've already contacted several downstreams: Sune for Debian, Will for >> OpenSUSE, Raphael for FreeBSD; the Fedora people were the originators of the >> bug report and have posted here. >> >> Al

Re: [Development] Retina display support

I updated https://bugreports.qt-project.org/browse/QTBUG-23870 with a longer description on Image/Pixmap drawing. If you resize manually you need to know if you are targeting a 1x or 2x display. Better to just specify the target rect and let Qt resize the image for you - Qt can do this if the

Re: [Development] Co-installation & library naming rules

On Friday, September 28, 2012 13:25:42 Thiago Macieira wrote: > I've already contacted several downstreams: Sune for Debian, Will for > OpenSUSE, Raphael for FreeBSD; the Fedora people were the originators of the > bug report and have posted here. > > All have given their +1 to the proposal. Than

Re: [Development] Harmattan - broken qmake

On Thursday, September 27, 2012 07:46:57 PM Laszlo Papp wrote: > > Can you do what it says? > > I have spent a couple of hours with figuring this problem out, and it > seems the following change in qmake has made the build policy about > errors stricter: > https://codereview.qt-project.org/#change

Re: [Development] Co-installation & library naming rules

On sexta-feira, 28 de setembro de 2012 15.14.32, Konstantin Tokarev wrote: > 23.09.2012, 18:06, "Thiago Macieira" : > > Because there is only one prefix for distributions: /usr. They do not like > > installing elsewhere. > > E.g. Mandriva istalls Qt 4 into /usr/lib/qt4 prefix, and Qt 3 to > /usr/li

Re: [Development] Qt5 Beta cross compiling problem

On sexta-feira, 28 de setembro de 2012 11.16.42, Thomas Senyk wrote: > > No, it shouldn't. It should be linux-g++-imx6. There are several sections > > of the .pro files that test for "--*", e.g. in simd.prf: > > > > *-g++*|linux-icc*|*-clang*|*-qcc* { > > A good to know! Thanks. > > But this is not

Re: [Development] Co-installation & library naming rules

On sexta-feira, 28 de setembro de 2012 13.07.16, Stephen Kelly wrote: > On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote: > > This is long, so I'll give you my recommendation first. If you agree with > > me, you don't have to read the rest. If you disagree, you have to read my > > argu

Re: [Development] Co-installation & library naming rules

23.09.2012, 18:06, "Thiago Macieira" : > Because there is only one prefix for distributions: /usr. They do not like > installing elsewhere. E.g. Mandriva istalls Qt 4 into /usr/lib/qt4 prefix, and Qt 3 to /usr/lib/qt3 -- Regards, Konstantin ___ Devel

Re: [Development] Branching for Qt 5 repositories

I think so, so I have to keep silent anymore. 2012/9/28 Stephen Kelly > Unfortunately there's no chance of changing it, I'm sure. -- *Please don't ask where I come from, It's a shame!* Best Regards Yuchen ___ Development mailing list Development@q

Re: [Development] Co-installation & library naming rules

On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote: > This is long, so I'll give you my recommendation first. If you agree with > me, you don't have to read the rest. If you disagree, you have to read my > arguments. It seems like the this thread and the 'Qt 5 file hierarchy' are really

Re: [Development] Branching for Qt 5 repositories

On Friday, September 28, 2012 12:37:23 Loaden wrote: > I prefer: > dev -> next > stable -> master > release -> release Me too. It's what git.git does and it's close to what cmake does. Unfortunately there's no chance of changing it, I'm sure. Thanks, -- Stephen Kelly | Software Engineer KDAB

Re: [Development] Co-installation & library naming rules

On Friday, September 21, 2012 04:47:11 PM Thiago Macieira wrote: > This is long, so I'll give you my recommendation first. If you agree with > me, you don't have to read the rest. If you disagree, you have to read my > arguments. > > Recommendation: > --- > > Include the major version

Re: [Development] Co-installation & library naming rules

On 27 September 2012 06:01, Lisandro Damián Nicanor Pérez Meyer wrote: > IIRC, in Debian with Qt3 and Qt4 we did have both libs installed without > problems. With respect the other stuff: > > - qmake, moc et al.: we used divertions (an apt facility) to let the user > choose which one to use on com

Re: [Development] Qt5 Beta cross compiling problem

On Thu, September 27, 2012 07:19:50 PM Thiago Macieira wrote: > On quinta-feira, 27 de setembro de 2012 18.37.18, Thomas Senyk wrote: > > Their is a naming convention for mkspecs ... not sure how it's definition > > looks exactly, but it should be named: linux-imx6-g++ > > No, it shouldn't. It sho

Re: [Development] Branching for Qt 5 repositories

From: development-bounces+andre.poenitz=digia@qt-project.org [development-bounces+andre.poenitz=digia@qt-project.org] on behalf of Loaden [loa...@gmail.com] > I prefer: > dev -> next > stable -> master > release -> release -1, and +1 for the originally proposed version. For someone wanti

Re: [Development] Branching for Qt 5 repositories

Thiago Macieira wrote: > On sexta-feira, 28 de setembro de 2012 09.06.42, Laszlo Papp wrote: >> > That's the point: it's not the most common way, at least not in Git. If >> > you >> > take for example Git's Git, the "master" branch contains the latest >> > release, whereas the next release is in th

Re: [Development] Branching for Qt 5 repositories

> I actually prefer Loaden's suggestion, Ok for me. > Yeah, right... We've been feature-complete for a while. So why is Qt 5.0.0 not > released yet? [skip] Yes, I am sorry for that. I did not get your point initially, but I understand your point now (see my other email). > We cannot design an i

Re: [Development] Branching for Qt 5 repositories

On sexta-feira, 28 de setembro de 2012 10.28.26, João Abecasis wrote: > No it is not a release. The point is features are developed outside > shared branches until the point where they are ready for wider > exposure. It doesn't mean they won't change. But it does mean the > feature does something u

Re: [Development] Branching for Qt 5 repositories

On sexta-feira, 28 de setembro de 2012 09.06.42, Laszlo Papp wrote: > > That's the point: it's not the most common way, at least not in Git. If > > you > > take for example Git's Git, the "master" branch contains the latest > > release, whereas the next release is in the "next" branch. > > Well, yo

Re: [Development] Branching for Qt 5 repositories

Laszlo Papp wrote: >> No, I really do and those qualifiers are required, but note that they apply >> to >> each feature individually. That is, if you want to merge the command-line >> parser, it needs to be feature-complete, working, documented, tested and a >> few >> more qualifiers (cf. Qt Proj

Re: [Development] Branching for Qt 5 repositories

> If those all fully apply, I would call it "release" since there is > nothing to fix anymore or stabilize since it is "completely". My point > is that there may be bugs on certain platforms where it is not well > tested, or the documentation is written and approved by developers and > cannot get b

Re: [Development] Branching for Qt 5 repositories

Sounds great, especially the branch names. +1 Simon From: development-bounces+simon.hausmann=digia@qt-project.org [development-bounces+simon.hausmann=digia@qt-project.org] on behalf of Thiago Macieira [thiago.macie...@intel.com] Sent: Thursday, S

Re: [Development] Branching for Qt 5 repositories

> That's the point: it's not the most common way, at least not in Git. If you > take for example Git's Git, the "master" branch contains the latest release, > whereas the next release is in the "next" branch. Well, you can say that it is not common, but I could enumerate quite a few examples inclu

Re: [Development] Branching for Qt 5 repositories

On 09/28/2012 07:37 AM, Loaden wrote: > I prefer: > dev -> next > stable -> master > release -> release +1 Ciao, Alberto -- http://blog.mardy.it <- geek in un lingua international! ___ Development mailing list Development@qt-project.org http://lists