Hi,
Practically, since Qt Project has no plan to support Qt5 in Harmattan,
I believe the Harmattan-specific code sits in its own clone repository
(same as for QtonPi [1] and ), right?
[1] https://qt.gitorious.org/qtonpi
Xizhi Zhu (Steven)
Software Engineer @ Qt Development Fram
On Wednesday, 11 de January de 2012 16.43.11, Thiago Macieira wrote:
> > "Subject" simply means "the string you're matching your regexp
> > against", so there's no confusion when one talks about "strings"
> > (there are the pattern string and the subject string).
>
> Ok. But then see below...
It d
On Wednesday, 11 de January de 2012 17.53.17, Giuseppe D'Angelo wrote:
> 2012/1/11 Thiago Macieira :
>
> Hi, thanks for the reply. :)
>
> > First, you'll need to get a Nokian to import the PCRE sources. You cannot
> > submit them to Gerrit (not even to the commit you made) because that
> > violates
2012/1/11 Thiago Macieira :
Hi, thanks for the reply. :)
> First, you'll need to get a Nokian to import the PCRE sources. You cannot
> submit them to Gerrit (not even to the commit you made) because that violates
> the CLA. You're not the author. Please don't submit the PCRE code again --
> just
On 01/09/2012 11:42 PM, ext Turunen Tuukka wrote:
>
> Hi All,
>
> My preference is to definitely have the Contributors Summit before
> summer in order to focus discussions into what should be in 5.1. So
> mid-May to mid-June is best, even though 5.0 is still on its way at that
> time. If we have th
On Wed, Jan 11, 2012 at 5:22 PM, wrote:
> I'd think one project could handle all the removed features we want to
> support as static libraries
> e.g.
> qftp
> qhttp
> qsettings
>
> "qt4support" isn't a terrible name, unless it has too bad connotations.
I don't really get what's wrong with that
>
> I'd say we should keep each independent class in its own static library
> build.
> So it would be "qftp" inside a kitchen sink repository.
>
I agree completely
Subject to local law, communications with Accenture and its affiliates
including telephone calls an
I'd think one project could handle all the removed features we want to support
as static libraries
e.g.
qftp
qhttp
qsettings
"qt4support" isn't a terrible name, unless it has too bad connotations.
"qt4removedapis" is clear as well
I'll take care of moving QHttp and QFtp.
In general, the person r
Hi,
I just wanted to inform you that we now run the wiki on the native mediawiki
crowd authenticator for single sign logon. This fixes QTWEBSITE-326. The
following issues are fixed:
- https links require logins
- impossible to log out from the wiki
- different beha
On Wednesday, 11 de January de 2012 14.48.55, lars.kn...@nokia.com wrote:
> Yes, please. We need a name for it. How about qtnetwork4 ?
>
> I people are ok with the name, can you add the repo, Sergio?
>
> Who'd be willing to import the code and examples into that repo? Shane?
I'd say we should keep
Yes, please. We need a name for it. How about qtnetwork4 ?
I people are ok with the name, can you add the repo, Sergio?
Who'd be willing to import the code and examples into that repo? Shane?
Thanks,
Lars
On 1/11/12 3:26 PM, "ext shane.kea...@accenture.com"
wrote:
>Can we get an addon module
Can we get an addon module (project in gerrit) for putting standalone
implementations of these removed features?
I wouldn't expect a huge amount of commits, but the code (and associated
examples/tests) needs to be moved there and converted from dll exports to
static libraries.
> -Original M
On Wednesday, 11 de January de 2012 16.39.52, Lincoln Ramsay wrote:
> On 01/11/2012 04:06 PM, ext Ismael Luceno wrote:
> > error: invalid static_cast from type 'QObject*' to type
> > 'QAndroidPlatformScreen*'
>
> Is this GCC 4.6 by any chance?
>
> I've had a report of it failing to compile some moc
On Wednesday, 11 de January de 2012 12.49.27, Giuseppe D'Angelo wrote:
> Up?
> Nobody wants to discuss this?
It's above the bikeshed threshold :-)
First, you'll need to get a Nokian to import the PCRE sources. You cannot
submit them to Gerrit (not even to the commit you made) because that violate
On Wednesday 11 January 2012 14:13:45 ext marius.storm-ol...@nokia.com wrote:
> In this particular case most of the contributions coming from Digia are
> contribs which were in Gitorious before, and them not being accepted put at
> least handled is our fault.
>
> I think for those its only fair
In this particular case most of the contributions coming from Digia are
contribs which were in Gitorious before, and them not being accepted put at
least handled is our fault.
I think for those its only fair that those are handled against 4.8, and then
forward ported to 5.0.
Once those origina
Up?
Nobody wants to discuss this?
Cheers,
--
Giuseppe D'Angelo
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 11.1.2012 13.00, "Oswald Buddenhagen"
wrote:
>On Wed, Jan 11, 2012 at 06:59:34AM +, ext Turunen Tuukka wrote:
>> But we will push these also to Qt 5, of course we want it to contain
>>these
>> fixes as well. We plan to do this after the review is done and we know
>>if
>> the fix is accept
Yes, if you think this is mostly an issue on initial show, (which I also think)
then I think such a solution would acceptable.
The default should then be AdjustToContentsOnFirstShow, as it is in QComboBox.
regards,
Jan-Arve
From: ext Christoph Schleifenbaum [mailto:christoph.schleifenb...@kdab.c
On Wed, Jan 11, 2012 at 06:59:34AM +, ext Turunen Tuukka wrote:
> But we will push these also to Qt 5, of course we want it to contain these
> fixes as well. We plan to do this after the review is done and we know if
> the fix is accepted.
>
and how exactly do you plan to ensure that nothing f
20 matches
Mail list logo
