On 3/8/12 4:22 PM, "ext Thiago Macieira" wrote:
>On quinta-feira, 8 de março de 2012 11.34.04, Alexis Menard wrote:
>> > So, the barrier for Qt5 is a compiler that supports C++0x? Not a bad
>>idea.
>>
>> I didn't said anything about C++0x and I seriously don't think this
>> should be the barrier
On 3/12/12 9:31 AM, "ext Jørgen Lind" wrote:
>> This will be hard to do with qmake, so the easier way out is to remove
>>the .a
>> altogether and use .pri files only. That requires moving the Wayland
>>platform
>> plugin back into qtbase.
>>
>Pretty please with sugar on top, do NOT do this. I
Hi Quim,
sounds good, please go ahead.
Cheers,
Lars
On 3/13/12 8:05 PM, "ext quim@nokia.com" wrote:
>(Sorry for top-posting from this web client)
>
>Thank you for the list of modules. Can I do the following changes to the
>wiki?
>
>1. Move the list of modules at
>http://qt-project.org/wiki
On 3/14/12 9:12 PM, "ext Holger Hans Peter Freyther"
wrote:
>On 03/07/2012 05:12 PM, Thiago Macieira wrote:
>> On quarta-feira, 7 de março de 2012 19.36.17, Rohan McGovern wrote:
>>> Thanks, so can we use #pragma GCC diagnostic to selectively silence
>>> warnings like this? There doesn't seem to
On 3/14/12 10:33 PM, "ext Holger Hans Peter Freyther"
wrote:
>On 03/14/2012 10:26 PM, lars.kn...@nokia.com wrote:
>
>>>
>>> tests/auto/other/headersclean
>
>> Only if someone provides a patch. I won't stop the alpha because of a
>> header file warning.
>
>it is a build breakage of the above test
On 3/15/12 8:13 PM, "ext Robin Burchell" wrote:
>2012/3/15 Thiago Macieira :
>> No one has objected. Can someone remove the deprecation marks in
>>QPointer,
>> please?
>
>Pushed to http://codereview.qt-project.org/#change,20203 :-)
And staged :)
Cheers,
Lars
___
Hi Tukka,
let's make this simple. You and Digia stepped up to make 4.8 patch level
releases. So far nobody else has, so the 'release manager' job simply
falls into your hands.
Adding some patches to the release and deciding what exactly goes out
should be at the discretion of the one doing the re
Hi everybody,
there are quite a few people meeting up in Oslo this week, and we'll try
to finish up the Qt 5 alpha there. For this reason I'd like everybody to
restrain themselves in what they submit to the master branch. The main
focus needs to be to get the alpha, so please focus on staging only
None of the below changes the fact that the xlib plugin is unmaintained
and broken. Removing it is the right thing to do for exactly that reason.
If things don't work with an older xcb release, let's add a configure test
requiring a minimum version that works. I rather have configure bail out
with
On 3/18/12 6:28 PM, "ext Bradley Smith" wrote:
>
>
>
>Every Linux distro uses X.org, which uses XCB.
>
>
>
> Including openSUSE 11.1, but just any XCB is not enough. It needs to be
>more recent than some version. For users with an incompatible version of
>XCB, I think we can provide a better use
On 3/18/12 9:05 PM, "ext Thiago Macieira"
wrote:
>On domingo, 18 de março de 2012 19.55.53, lars.kn...@nokia.com wrote:
>> * No more source incompatible changes to features/API that are new in Qt
>> 5, unless approved by the module's maintainer after a discussion on the
>> mailing list
>
>Does th
On 3/19/12 2:11 AM, "ext Rohan McGovern" wrote:
>marius.storm-ol...@nokia.com said:
>> While it's not normal to do this type of dependency "lock" for upwards
>>dependencies, i think in this case we should indeed do the extra
>>checking. Not just because QtDeclarative is such an important tech for
On 3/19/12 9:19 AM, "ext Thorbjørn Martsum" wrote:
>Hi Lars
>
>You are the boss :) - and I am not disagreeing that this should happen
>rather sooner then later (it is actually happening very late if the final
>release plan still says june),
>but I however think it would be better (in the future)
Longer term, I think we should have one qmoduleglobal.h per shared library, and
have the additional enums in there. Nothing speaks against them living in the
same namespace though IMO, but we'll need to sort out how qdoc handles this.
One idea might be to handle the namespace similar to inherita
On 3/28/12 7:06 PM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 28 de março de 2012 15.37.46, Marc Mutz wrote:
>> So I'd like to propose to extend the scope of Q_PRIMITIVE_TYPE to cover
>>such
>> non-POD classes that are nevertheless close enough to PODs.
>>
>> That means:
>> 1a. memset(0, &t
I'll try to go through them tonight.
Lars
On 3/28/12 8:02 PM, "ext Thiago Macieira"
wrote:
>The new QUrl has been up for review for several days now. Lots of people
>have
>commented on the basic enablers and I have taken into account a lot of
>feedback.
>
>But as the principle of bikeshed goes
All is reviewed. Stage at your convenience ;-)
Cheers,
Lars
On 3/28/12 11:42 PM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 28 de março de 2012 19.08.04, lars.kn...@nokia.com wrote:
>> I'll try to go through them tonight.
>
>Thanks for the effort. I've gone over all the recommendations and
Approved. Sergio, can you help setting it up, please?
Thanks,
Lars
On 3/29/12 2:50 AM, "ext wolfgang.b...@nokia.com"
wrote:
>Hi guys,
>
>I'm following the steps on
>http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
>To get a playground project created for qlogger in place.
>
>qlog
No, currently I do not want hundreds of feature branches on qtbase. We
need to focus on stabilization and not doing new features.
And if the people working on the logging FW want to release it to others
as an add-on to 5.0 why do you want to stop them?
Lars
On 3/29/12 11:18 AM, "ext Oswald Budde
+2 ;-)
Cheers,
Lars
On 3/30/12 2:41 PM, "ext marius.storm-ol...@nokia.com"
wrote:
>+1, and first!
>
>--
>.marius
>
>
>> -Original Message-
>> From: development-bounces+marius.storm-olsen=nokia.com@qt-
>> project.org [mailto:development-bounces+marius.storm-
>> olsen=nokia@qt-projec
On 3/31/12 10:19 AM, "ext Olivier Goffart" wrote:
>On Friday 30 March 2012 15:35:40 Thiago Macieira wrote:
>> On sexta-feira, 30 de março de 2012 18.41.46, Olivier Goffart wrote:
>> > On Friday 30 March 2012 12:23:59 Thiago Macieira wrote:
>> > > Use of QVarLengthArray should *only* be done with
On 3/31/12 6:41 PM, "ext Giuseppe D'Angelo" wrote:
>2012/3/31 Thiago Macieira :
>> On sábado, 31 de março de 2012 17.00.17, Davet Jacques wrote:
>>> Out of interest: Has there been a final decision to keep the name
>>> QRegularExpression (rather than QRegex)?
>>
>> I like the name.
>>
>> And I es
I was never a really big fan of adding lots of virtual_hook()'s to
classes. vtable entries do come at a cost and in many cases it's not
really required. I am certainly against blindly adding them to all our
classes.
Cheers,
Lars
On 4/11/12 8:19 AM, "ext jan-arve.saet...@nokia.com"
wrote:
>The "
Hi everybody,
hope many of you had the chance to take some time off over easter. I
certainly did.
Now that the alpha is out, there's work we need to do to get things in
shape for a beta.
We are now done with new feature development and changes to our API. I
will merge the api_changes branch that
It's been now a couple of weeks and Girish had the supporting votes.
So congratulations Girish to becoming an Approver!
Cheers,
Lars
On 3/6/12 10:06 AM, "Lars Knoll" wrote:
>Hi,
>
>I'd like to nominate Girish for Approver status. He's been around Qt for a
>pretty long time, working for Trollte
On 4/12/12 6:05 AM, "ext Alex Wilson" wrote:
>On Wednesday, April 11, 2012 07:25:41 pm ext BogDan wrote:
>> the problem with QML desktop components is that
>> not all controls are touch friendly (e.g. lists, editbox, etc.), even
>>they
>> have Android look the feel is not the right one. As I said
On 4/12/12 3:39 PM, "ext Girish Ramakrishnan"
wrote:
>Hi Lars,
>
>On Wed, Apr 11, 2012 at 5:49 AM, wrote:
>> Hi everybody,
>>
>> hope many of you had the chance to take some time off over easter. I
>> certainly did.
>>
>> Now that the alpha is out, there's work we need to do to get things in
>>
On 4/12/12 5:06 PM, "ext Oswald Buddenhagen"
wrote:
>On Thu, Apr 12, 2012 at 04:26:12PM +0200, ext Stephen Kelly wrote:
>> I'd like to see another model attempted next time, like all commits
>> going to master, and a 'stable' branch which gets fast forwarded once
>> a week
>>
>that's besides th
On 4/12/12 7:27 PM, "ext casper.vandonde...@nokia.com"
wrote:
>>> There are 2 main problems with the current system:
>>> 1. Nobody was running "make docs" on their local machines (and
>>>verifying the
>>> output). There are qdoc errors that were put in by developers last
>>> December. Having the
On 4/12/12 4:09 PM, "ext Olivier Goffart" wrote:
>On Thursday 12 April 2012 15:35:45 André Somers wrote:
>> Op 12-4-2012 15:12, casper.vandonde...@nokia.com schreef:
>> > Modularizing the documentation is a process that will move a lot of
>>files
>> > around and make some things impossible.
>> >
On 4/13/12 7:18 PM, "ext Samuel Rødal" wrote:
>On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>> I am going through all the new apis. I have a couple of more changes
>> to the public apis already. I am not submitting them to api_changes
>> branch. I think Lars and co are having eno
On 4/14/12 8:29 PM, "ext BogDan" wrote:
>Hello,
>
>I checked QPlatformInputContext interface and I think it needs more
>informations
Not sure what you're missing. QPlatformInputContext is only there to
implement support for an input method, and has received quite some testing.
QInputMethod (s
On 4/15/12 12:35 PM, "ext Uwe Rathmann" wrote:
>Hi Thiago,
>
>my interest is of course to benefit as much as possible from the ideas
>and solutions of the Qt development
>and I believe the best way should be to organize my code and build
>environment like Qt libraries do.
>
>So please let me chec
On 4/16/12 2:15 PM, "ext Michael Jansen" wrote:
>On Sunday, April 15, 2012 08:40:38 PM Thiago Macieira wrote:
>> On segunda-feira, 16 de abril de 2012 01.33.31, Stephen Kelly wrote:
>> > > The only applications that should do that are the workspace fixture
>> > > ones:
>> > > kwin and plasma.
>
On 4/17/12 9:59 AM, "ext Olivier Goffart" wrote:
>On Sunday 15 April 2012 20:38:22 Thiago Macieira wrote:
>> On segunda-feira, 16 de abril de 2012 00.08.43, Olivier Goffart wrote:
>> > On Saturday 14 April 2012 20:06:53 Giuseppe D'Angelo wrote:
>> > > So, after *too many* commits[1] -- QHash rand
Hi everybody,
the merge of api_changes back into master for qtbase finally made it's way
through the CI system. I'm currently in the process of merging declarative
back and Kent is staging all the changes required to fix compilation of
the other modules.
>From now on most changes should go to mas
On 4/17/12 1:15 AM, "ext Thiago Macieira"
wrote:
>On segunda-feira, 16 de abril de 2012 21.31.52, Fredrik Höglund wrote:
>> On Monday 16 April 2012, Thiago Macieira wrote:
>> > On segunda-feira, 16 de abril de 2012 00.02.21, Stephen Kelly wrote:
>> > > Can you point me to it? Does it contain a eq
On 4/17/12 9:58 PM, "ext Thiago Macieira"
wrote:
>On terça-feira, 17 de abril de 2012 15.37.35,
>marius.storm-ol...@nokia.com
>wrote:
>> Yes, it does.
>> And for the case of QPA, we have said that we don't want to promise BC,
>>but
>> we haven't said that we will go around breaking SC for every p
Proposal sounds ok to me as well. If someone still has concerns, please
speak up.
Cheers,
Lars
On 4/20/12 9:02 AM, "ext Samuel Rødal" wrote:
>On 04/18/2012 04:03 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>>
>> On Wed, Apr 18, 2012 at 3:28 AM, wrote:
>>> Still the QPA headers are sort of a di
On 4/22/12 9:14 AM, "ext d3fault" wrote:
>Yes, it is strongly biased due to the wording. Fix the wording and post
>it anyways. The numbers will not change.
>
>I got bored and drew a pretty picture to summarize my feelings for QML:
>http://bayimg.com/jaooAAaDC
>
>Hope you laugh.
>
>But back to bei
On 4/24/12 9:53 AM, "ext casper.vandonde...@nokia.com"
wrote:
>Hi,
>
>I just cut out the rest of the email for clarity. (great that you would
>want to help)
>
>I just want to talk about the inherits and inherited by problem.
>"Inherits" should always work, because you compile the Qt code that way
I'm with Olivier here. The default meaning in 4.x was :fromLatin1() (if
you didn't use setCodecForCStrings()), so we could simply leave that
behavior and simply deprecate the API.
Cheers,
Lars
On 4/24/12 3:36 PM, "ext Olivier Goffart" wrote:
>On Tuesday 24 April 2012 14:27:10 Thiago Macieira wr
On 4/25/12 3:11 PM, "ext Olivier Goffart" wrote:
>On Wednesday 25 April 2012 13:47:35 Thiago Macieira wrote:
>> However, I agree with you: it's too late to change it everywhere.
>>Unless we
>> do it properly, it also has the potential to make things worse. I'd
>>like to
>> ask you to find out whe
On 4/30/12 2:53 PM, "ext Thiago Macieira"
wrote:
>On segunda-feira, 30 de abril de 2012 14.14.00, Kent Hansen wrote:
>> Yes, it's late, but it's also one of the final nails in the const char
>> *-based Q(Meta)Object introspection API coffin.
>[snip the rest]
>
>Needless to say, I support this cha
On 4/30/12 4:10 PM, "ext Giuseppe D'Angelo" wrote:
>On 30 April 2012 15:07, Thiago Macieira wrote:
>> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
>>> Just a notice to all devs:
>>>
>>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on
>>>Wednesday, all
>>> Qt
On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com"
wrote:
>
>On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote:
>
>> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote:
>>> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote:
On segunda-feira, 30 de abril de 2012 16.58.0
Hi everybody,
While I think it's very important to get Qt 5.0 out of the door as soon as
possible, we should not release it without first getting it's quality to a
very high standard.
I think it has become rather clear that the original timeline of releasing
Qt 5.0 by mid June is not doable anymo
On 5/2/12 10:48 AM, "ext Thiago Macieira"
wrote:
>Given the negative reaction here and on Gerrit, I'm wondering if we
>should
>revert it.
>
>In fact, for the simple fact that the SIC change wasn't discussed here
>before
>it went in (my bad, sorry for that), it deserves to be reverted.
My bad a
On 5/2/12 11:57 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 2 de maio de 2012 10.21.36, Giuseppe D'Angelo wrote:
>> In a related patch I suggested something like
>>
>> int QRegExp::foo() const
>> {
>> QRegExp copy = *this;
>> return copy.foo();
>> }
>>
>> which although being source
On 5/2/12 5:22 PM, "ext simon.hausm...@nokia.com"
wrote:
>I believe changing the string in Q_DECLARE_INTERFACE is binary
>incompatible but fully source compatible.
And actually we do want them to be binary incompatible to 4.x. Currently I
do see warnings about some qt 4.x image format or style p
On 5/8/12 12:08 PM, "ext Frank Hemer" wrote:
>On Tuesday 08 May 2012 09:50:16 Peter Kuemmel wrote:
>> > > Now we suddenly have an easy to use, yet compulsory, Turing complete
>> > > language with essentially no support from off-the-shelf tools.
>> >
>> > It's this "compulsory" part that I don't u
On 5/9/12 12:33 PM, "ext Olivier Goffart" wrote:
>On Wednesday 09 May 2012 11:28:30 Giuseppe D'Angelo wrote:
>> On 9 May 2012 10:22, Olivier Goffart wrote:
>> > On Wednesday 09 May 2012 09:45:31 Andreas Holzammer wrote:
>> >> Hi,
>> >>
>> >> I was hitting qtxmlpatterns not compiling, because Ex
On 5/9/12 4:30 PM, "ext Thiago Macieira" wrote:
>On quarta-feira, 9 de maio de 2012 11.30.35, lars.kn...@nokia.com wrote:
>> Actually I wonder why we don't compile all of Qt with exceptions
>>disabled
>> by default and enable them only for the places they are really needed
>> (QtCore for exceptio
On 5/10/12 4:20 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 9 de maio de 2012 21.39.53, lars.kn...@nokia.com wrote:
>> How about this then?
>>
>> https://codereview.qt-project.org/#change,25788
>>
>> https://codereview.qt-project.org/#change,25787
>
>Yes, something like that. I'm not sur
On 5/10/12 5:59 AM, "ext Girish Ramakrishnan"
wrote:
>Hi Lars,
>The current API appears to make modifications to values instead of the
>document itself. This makes it quite cumbersome to modify a document.
>For example, to change the value of 5 to 10 in the json "[1, 2, [3, 4,
>[5, 6]]]", one has
On 5/10/12 10:47 AM, "ext Joerg Bornemann"
wrote:
>On 09/05/2012 09:45, ext Andreas Holzammer wrote:
>
>> I was hitting qtxmlpatterns not compiling, because Exceptions are not
>> enabled by default for Windows CE. My guess is that this was done for
>> performance and or security reasons.
>
>We've
On 5/10/12 5:13 PM, "ext Olivier Goffart" wrote:
>On Thursday 10 May 2012 07:10:51 lars.kn...@nokia.com wrote:
>> On 5/10/12 4:20 AM, "ext Thiago Macieira"
>>
>> wrote:
>> >On quarta-feira, 9 de maio de 2012 21.39.53, lars.kn...@nokia.com
>>wrote:
>> >> How about this then?
>> >>
>> >> https:/
On 5/11/12 12:51 AM, "ext Thiago Macieira"
wrote:
>On quinta-feira, 10 de maio de 2012 20.17.34, lars.kn...@nokia.com wrote:
>> If we really want to remove that overhead the better option would
>>probably
>> be to only compile the files that need it with exceptions enabled.
>
>That's a task for t
On 5/11/12 11:30 AM, "ext kai.koe...@nokia.com"
wrote:
>> -Original Message-
>> From: development-bounces+kai.koehne=nokia@qt-project.org
>> [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
>> Behalf Of ext Stephen Kelly
>> Sent: Friday, May 11, 2012 11:19 AM
>> To:
On 5/14/12 11:27 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 2 de maio de 2012 15.22.16, simon.hausm...@nokia.com
>wrote:
>> I believe changing the string in Q_DECLARE_INTERFACE is binary
>>incompatible
>> but fully source compatible.
>
>> The string gets embedded in moc generated code as
Full support from my side for it.
Cheers,
Lars
On 5/14/12 1:11 PM, "ext Thiago Macieira"
wrote:
>I'd like to deprecate those two functions, as well as the setters
>QFile::setEncodingFunction and setDecodingFunction. I'd like to go
>further and
>make the setters no-op, and the actual functions
Hi Thiago,
reading through the whole thread, I am leaning towards proposal 2. It
might be slightly more difficult to document, but has less API clutter and
is probably easier for us to maintain in the longer term.
Cheers,
Lars
On 5/14/12 6:29 PM, "ext Thiago Macieira"
wrote:
>Hello
>
>David an
I don't want to maintain a fork of phonon on qt-project if the developers
decided they want to continue within the KDE infrastructure. phonon should
have one upstream place where it is being developed.
I'd say let's deprecate the module and remove it from qt5.git. We can keep
the code around for s
On 5/17/12 8:36 PM, "ext Stephen Kelly" wrote:
>On Thursday, May 17, 2012 18:31:43 lars.kn...@nokia.com wrote:
>> I don't want to maintain a fork of phonon on qt-project if the
>>developers
>> decided they want to continue within the KDE infrastructure. phonon
>>should
>> have one upstream place
A few comments from my side:
* I am not a big fan of inlining the public classes neither. It feels a
bit like over-optimizing at the wrong place. Reason is that this might
make it a impossible later on to refactor our code.
* It's ok to have some low level inline class for internal use if that
hel
I'd appreciate if you could stop your ranting on the mailing list.
I believe most people here are happy to participate in constructive
discussions but your rants will not achieve anything.
Lars
On 5/22/12 10:53 AM, "ext d3fault" wrote:
>I think we need a slogan change so as not to lie to our u
On 5/22/12 11:39 AM, "ext Uwe Rathmann" wrote:
>On 05/22/2012 10:53 AM, d3fault wrote:
>
>> Old Slogan: Code Once. Create More. Deploy Everywhere.
>
>I'm afraid the options will be: code twice or to deploy not everywhere.
>
>While Qt4 widgets were a full replacement of Qt3 widgets it is not clear
Hi everybody,
Honglei has so far been the maintainer for QtSql and QtXmlPatterns. He is
now leaving Nokia to start some studies and has told me that he can't
continue to maintain the modules.
I've been looking around for two new maintainers for these modules and
found two people that I'd like to
On 5/23/12 11:32 PM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 23 de maio de 2012 13.30.05, 1+1=2 wrote:
>> In addition, this will improve the unicode handling ability of Qt
>> tools with using bootstrap. Otherwise, tools such as qmake can not
>> deal with UTF-8 encoded files.
>
>That is ir
On 5/24/12 10:25 AM, "ext Thiago Macieira"
wrote:
>On quinta-feira, 24 de maio de 2012 08.17.03, frederik.gladh...@nokia.com
>wrote:
>> The problem I am seeing is that Qt prints for every Qt application this:
>> Qt: Untested Windows version 6.2 detected!
>
>Oh, that's sure going to get some peopl
On 5/24/12 11:38 PM, "ext Thiago Macieira"
wrote:
>On quinta-feira, 24 de maio de 2012 13.15.16, 1+1=2 wrote:
>> If we want to bootstrap tool such as qmake support utf8
>
>Why would we want to?
One reason could be paths/filenames that are encoded in the .pro file. If
we interpret it as latin1, w
I agree with Andre. Currently we do not have any guiding criteria in
place, so it's probably difficult to judge when someone is ready to be
nominated as an approver. We've now had one or two cases where people
where being nominated a bit too fast for my taste.
But I'd propose that we have a discu
Hi Jerome,
I'd say let's give him a bit more time to show the work he's doing. So far
his contributions aren't very visible in the community. He can already do
reviews inside the project (giving +1/-1) to changes, something that
should help you in reviewing.
With some contributions and active hel
On 5/25/12 9:41 AM, "ext Thiago Macieira"
wrote:
>On sexta-feira, 25 de maio de 2012 06.27.13, lars.kn...@nokia.com wrote:
>> I agree with Andre. Currently we do not have any guiding criteria in
>> place, so it's probably difficult to judge when someone is ready to be
>> nominated as an approver
On 5/25/12 9:37 AM, "ext Thiago Macieira"
wrote:
>On sexta-feira, 25 de maio de 2012 06.27.05, lars.kn...@nokia.com wrote:
>> On 5/24/12 11:38 PM, "ext Thiago Macieira"
>>
>> wrote:
>> >On quinta-feira, 24 de maio de 2012 13.15.16, 1+1=2 wrote:
>> >> If we want to bootstrap tool such as qmake s
On 5/26/12 9:57 AM, "ext jason.mcdon...@nokia.com"
wrote:
>> I would like to nomimate Miikka Heikkinen from Digia for Approver
>>status.
>>
>> He has been working on Qt 5 on Windows for a quite a while and has fixed
>> numerous issues and failing test cases in the areas QWidget/QWindow,
>> fonts,
On 5/24/12 1:31 PM, "ext Shaw Andy" wrote:
>[snip]
>
>> >The warning needs to go away, at least, provided that Qt *is* tested on
>> >Windows 8. Whether we add the enum or not, that's a bit orthogonal.
>>
>> Yes, the warning needs to be fixed.
>>
>> But I don't have any problems with adding the
On 5/29/12 8:22 AM, "ext Jørgen Lind" wrote:
>Hi
>> 6. Rename the handle() to platformXXX() since it's easy to educate
>> that anything that has platform in it is out of reach of app
>> developers.
>> Status: In progress, I am atm, marking handle() as obsolete and as an
>> alias to platformXXX().
Sounds like something left over from the past. I agree that we should fix
that for 5.0.
Cheers,
Lars
On 5/31/12 12:46 PM, "ext Flex Ferrum" wrote:
>Hello all.
>
>Does anybody know why Qt still shipping with /Zwchar_t- flag for MSVC
>compilers (even for MSVC 2010)? It makes difficult to use Qt w
Unfortunately it took a bit longer than I thought to get binary packages.
So yes, an alpha 2 might not make as much sense anymore as we had hoped
for.
Now that we have the packages, I think our main focus should be to get the
beta out. From the implementation side I think we're in an ok shape for
I think this is the doing things the wrong way round. There's exactly one
small designer plugin depending on QtQuick1 (and pulling in qtscript), so
what we should rather do is to move that plugin out of qttools and into
qtquick1. That should reverse the dependency order and would be a lot more
logi
On 6/6/12 1:56 PM, "ext Sean Harmer" wrote:
>On Wednesday 06 June 2012 13:22:21 Thiago Macieira wrote:
>> On quarta-feira, 6 de junho de 2012 11.46.18, Sean Harmer wrote:
>> > What other gates do we also have to pass to promote QNX to Tier 1?
>>
>> The major target is that, at release time, you'
Can't remember that you asked me. I can certainly review them if you don't have
anyone else. I'll do so later tonight.
Cheers,
Lars
On 06.06.12 18:54 ext Thiago Macieira wrote:
Cf. thread: Maintainer "TrustMes"
http://lists.qt-project.org/pipermail/development/2012-April/002930.html
http://l
On 6/6/12 7:33 PM, "ext Thiago Macieira" wrote:
>On quarta-feira, 6 de junho de 2012 17.08.29, lars.kn...@nokia.com wrote:
>> Can't remember that you asked me. I can certainly review them if you
>>don't
>> have anyone else. I'll do so later tonight.
>
>I asked on IRC how you felt about reviewing
On 6/6/12 6:53 PM, "ext Thiago Macieira" wrote:
>Cf. thread: Maintainer "TrustMes"
>http://lists.qt-project.org/pipermail/development/2012-April/002930.html
>http://comments.gmane.org/gmane.comp.lib.qt.devel/2953
>
>I need help again reviewing my own changes. Since I am the maintainer of
>the
>m
On 6/7/12 12:55 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 6 de junho de 2012 21.56.16, lars.kn...@nokia.com wrote:
>> >https://codereview.qt-project.org/26981-Optimisedeletion
>>
>> I might be wrong (getting tired), but I think this reintroduces the
>> problem with forward declared poin
On 6/7/12 8:35 AM, "ext Rohan McGovern" wrote:
>Molkentin Daniel (Nokia-MP/Berlin) said:
>>
>> > It means that the current CI infrastructure is operated by Nokia and
>> > can't have build nodes plugged in from outside of Nokia premises. So,
>> > if you need to manage your own build nodes, there
On 6/6/12 9:21 PM, "ext Oswald Buddenhagen"
wrote:
>On Wed, Jun 06, 2012 at 04:51:14PM +0200, ext João Abecasis wrote:
>> Thiago Macieira wrote:
>> > So you're asking that filenames be passed on the locale encoding
>>(say, UTF-8)
>> > on the command-line, regardless of what the filesystem enco
Another +1. Konstantin has done a lot of good work on unicode and text
handling over the years.
Cheers,
Lars
On 6/7/12 9:43 PM, "ext André Pönitz"
wrote:
>On Thu, Jun 07, 2012 at 10:43:45AM -0700, Girish Ramakrishnan wrote:
>> Hi all, I would like to nominate Ritt Konstantin for approver status
On 6/7/12 9:27 PM, "ext Thiago Macieira" wrote:
>On quinta-feira, 7 de junho de 2012 11.09.52, 1+1=2 wrote:
>> Hi Thiago,
>>
>> The real problem is caused by MSVC2005, as they can't generate UTF-8
>> exec-charset.
>>
>> >From MSVC2010-SP1, they provided a workaround for this:
>> 1) Source fil
Hi Zoltan,
that's great news. Thanks for creating these packages.
On 6/8/12 11:23 AM, "ext Zoltán Balogh"
wrote:
>On 06/08/2012 12:10 PM, a.gra...@gmail.com wrote:
>> Hi,
>>
>> On 8 June 2012 12:05, Zoltán Balogh wrote:
>>> Hi all,
>>>
>>> I guess we all are very excited about the upcoming Qt5
On 6/10/12 9:45 PM, "ext Thiago Macieira"
wrote:
>On domingo, 10 de junho de 2012 20.44.05, David Faure wrote:
>> Is it really desired to break source compat so much, after making the
>> promise of "almost no porting required"? Porting to a different plugin
>> framework doesn't sound trivial. Wel
On 6/11/12 8:17 AM, "ext Simon Hausmann" wrote:
>On Wednesday, May 23, 2012 09:02:00 AM ext Simon Hausmann wrote:
>> Hi,
>>
>> I would like to nominate Peter for approver status.
>>
>> As part of the team in the University of Szeged he has completed the
>>past
>> few rebases of V8 in the qtjsba
3 weeks have passed, so congrats Miikka!
Cheers,
Lars
On 5/26/12 10:17 AM, "ext lars.kn...@nokia.com"
wrote:
>On 5/26/12 9:57 AM, "ext jason.mcdon...@nokia.com"
> wrote:
>
>>> I would like to nomimate Miikka Heikkinen from Digia for Approver
>>>status.
>>>
>>> He has been working on Qt 5 on Win
On 6/13/12 4:00 PM, "ext shane.kea...@accenture.com"
wrote:
>Background:
>If accept() returns an error, QTcpServer may live lock. (QTBUG-24778)
>The problem as described is that accept() returns EMFILE when quota is
>reached.
>On returning to the event loop, select() triggers again because the
>i
Let's do that please.
Lars
On 6/13/12 11:14 PM, "ext daniel.molken...@nokia.com"
wrote:
>
>On Jun 13, 2012, at 22:20 , ext Thiago Macieira wrote:
>> tst_QDnsLookup was failing again due to changes to gitorious.org's
>>public DNS.
>
>We can add a bogus qt-project.org sub-zone for testing purpose
On 6/26/12 10:59 AM, "ext Giuseppe D'Angelo" wrote:
>Well, 15 working days have passed since nomination + backing, and no
>objections were sent to the list.
>
>I guess that's enough for welcoming Sean Harmer as a new Approver in
>the Qt Project? :-)
Yes :)
Congratulations Sean!
Lars
_
On 6/26/12 11:59 AM, "ext Sean Harmer" wrote:
>On Tuesday 26 June 2012 09:49:27 lars.kn...@nokia.com wrote:
>> On 6/26/12 10:59 AM, "ext Giuseppe D'Angelo" wrote:
>> >Well, 15 working days have passed since nomination + backing, and no
>> >objections were sent to the list.
>> >
>> >I guess that'
Hi everybody,
first of all thanks to everybody who came and participated at the
contributor summit. I got a bit too much sidetracked and missed many of
the technical discussions I wanted attend. But it's great to see the notes
and summaries from the different sessions flow in now, and it shows tha
Short note while on vacations... ;-)
It was a conscious choice by me not to even try to split up QAction.
QAction is very much bound to widgets and I am not convinced at all it's
what we would need in QML.
I think we would be better served in rethinking what is required for Qt
Quick and QML compo
1 - 100 of 325 matches
Mail list logo
