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
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
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 think that's a valid point :-) They are all inside qtbase because of
> convenience. The build system wasn't and still isn't very friendly
> when it comes to creating separate modules.
I honestly dont understand this point. And why does it have to be a
submodule. Cant it just be a git repo wi
Den 25. mai 2012 02:35, skrev ext christopher.ad...@nokia.com:
> Hi,
>
>>> In QtQuick 2.0 (ie, Qt 5.0), we are thinking about using property var
>>> more often in the implementation (eg, of qobject-derived-type
>>> properties) to avoid some of those edge-cases, and providing more
>>> consistent (an
Hi,
> > In QtQuick 2.0 (ie, Qt 5.0), we are thinking about using property var
> > more often in the implementation (eg, of qobject-derived-type
> > properties) to avoid some of those edge-cases, and providing more
> > consistent (and useful) referencing semantics.
>
> Can you say what 'var' is an
Hey Jorgen,
I also like the idea of "default" plugins where eglfs will default to
loading support for the keyboard and an input device. I think having
some kind of heuristic for this will probably be gross, hacky and
harder to fathom than Girish's current approach which is baking it in.
There are
Hi, if you want to assure your Qt Contributors Summit shirt for your
size (and gender) you should REGISTER BEFORE THE END OF TUESDAY, MAY 29.
http://qt.nokia.com/forms/summit-signup
NOTE
We haven't rejected anybody so far. A few people has clicked "Join
group" at http://qt-project.org/groups/q
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?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556
I wrote
>Im having a similar issue, but a bit farther off the beaten path. Im on
VS2008, but trying to cross compile for Wince.
Found the issue.
The problem was the parameters for syncqt. The link Rohan posted had stuff
like:
Project MESSAGE: c:\test\recipes\187508955\base\qtbase\bin\syncqt
Hi all.
I'd like to propose the following addition to the "How to become an
Approver" section on http://qt-project.org/wiki/The_Qt_Governance_Model:
"Nomination for Approver status requires contribution or maintenance
of a significant amount of code, or comparable activitities
directly a
On Thu, May 24, 2012 at 12:47 PM, Thiago Macieira
wrote:
> For user applications (that is, other than qmake, moc, uic, etc.) that turned
> off QTextCodec, there's nothing that we can do. If you turn off the concept of
> codecs, then you can't change it.
>
Then
If we want to bootstrap tool such as
On Thu, May 24, 2012 at 12:47 PM, Thiago Macieira
wrote:
> You misunderstand Latin 1 then. If you read the contents with Latin1 and write
> using Latin1, you get exactly what you had before. No data is lost.
>
I know Latin1, I just forget that QString::toLocal8Bit() always equals
QString::toLatin
Hi Rene,
Thanks for the email. I think you raise some valid points. Some work on
addressing them is already underway.
On Wednesday, May 23, 2012 12:25:42 Rene Jensen wrote:
> Disclaimer 3: Discussing QML seems very poisonous these days, but I
> still feel the need for a thread that focus on the
On Thursday, May 24, 2012 02:41:31 christopher.ad...@nokia.com wrote:
> In QtQuick 2.0 (ie, Qt 5.0), we are thinking about using property var more
> often in the implementation (eg, of qobject-derived-type properties) to
> avoid some of those edge-cases, and providing more consistent (and useful)
>
On quinta-feira, 24 de maio de 2012 12.05.47, 1+1=2 wrote:
> When QT_NO_TEXTCODEC is defined, default codec is
> QTextCodec::codecForLocale(), but can be changed using
> QTextStream::setCodec().
I don't see the need to change then. It should remain the locale.
> When QT_NO_TEXTCODEC isn't defined
On Thu, May 24, 2012 at 10:26 AM, Thiago Macieira
wrote:
> On quinta-feira, 24 de maio de 2012 10.05.50, 1+1=2 wrote:
>> At present, when QT_NO_TEXTCODEC is defined, QTextStream use
>> QString::fromLatin1() /QString::toLocal8Bit()
>> to convert from/to bytes which looks like not very well. So I th
On quinta-feira, 24 de maio de 2012 10.05.50, 1+1=2 wrote:
> At present, when QT_NO_TEXTCODEC is defined, QTextStream use
> QString::fromLatin1() /QString::toLocal8Bit()
> to convert from/to bytes which looks like not very well. So I think it
> will be better to replace them with QUtf8::convertFrom
On Thu, May 24, 2012 at 2:51 AM, wrote:
> Not true. We do compile qutfcodec into qmake and the bootstrap tools, so
> QString::fromUtf8() does work. With the change of QString(const char *)
> to convert from utf8 I would assume that qmake at least partially uses
> utf8 by now.
>
> I think it make
On quinta-feira, 24 de maio de 2012 16.33.53, Olivier Goffart wrote:
> > I've long wanted to make QSharedPointer on QObject-derivatives participate
> > in the whole-tree ownership, somehow. I introduced QSharedPointer in 4.4
> > and I did some work in 4.5 to make that work.
> >
> > My original solu
Hi Rene,
On Wed, May 23, 2012 at 1:25 PM, Rene Jensen wrote:
>
> DOCUMENTATION...
>
> The truth is that initially in ten out of ten cases I resorted to
> guessing about the type and ownership of a value when I cross a
> boundary. Since I have thoroughly cross examined the docs, it must
> mean tha
Hi Jorgen/Laszlo,
On Thu, May 24, 2012 at 12:26 AM, Jørgen Lind wrote:
> On Wed, May 23, 2012 at 11:54:18PM -0700, ext Girish Ramakrishnan wrote:
>> Hi,
>>
>> On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
>> > I think we should focus on keeping eglfs as small as possible, but
>> > keeping
On Wednesday 23 May 2012 13:43:22 Thiago Macieira wrote:
> On quarta-feira, 23 de maio de 2012 14.16.12, Alberto Mardegan wrote:
> > On 05/23/2012 01:25 PM, Rene Jensen wrote:
> > > Question: How can we expose objects governed by QSharedPointer to QML
> > > safely? I can guarantee the lifecycle bey
On quinta-feira, 24 de maio de 2012 16.26.19, Olivier Goffart wrote:
> > Then you would also be able to make the "delete" operator work
> > consistently with reference-counted QObjects, by overriding it and make
> > it just decrement the count (and delete the object if the count is 0).
>
> No. That
On Thursday 24 May 2012 11:46:05 Alberto Mardegan wrote:
> On 05/23/2012 02:43 PM, Thiago Macieira wrote:
> > My original solution was to have a parent only deref its children's shared
> > pointer counter, deleting it only if it became zero. That means that if
> > you
> > had a QSharedPointer to an
Gerrit is working for me.
Your error message suggests that you are connecting to the bastion host,
instead of using it as a proxy.
The server fingerprint is shown on
https://codereview.qt-project.org/#settings,ssh-keys
And doesn't match what you have below.
--
> -Original Message-
> Fr
On 24.5.2012 15.32, "Thiago Macieira" wrote:
>On quinta-feira, 24 de maio de 2012 12.13.31, Yan Shapochnik wrote:
>> Since you are back porting this change to 4.8, I would also like to
>>make a
>> suggestion and include Mac OS X 10.8 Mountain Lion support in the same
>> manner.
>
>Yes, makes sen
On quinta-feira, 24 de maio de 2012 07.51.15, Carl Schumann wrote:
> Is this unavailability over? Anyone have indications of problems?
> Thanks for any insights please.
It's working for me. I've just pushed a commit.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
Qt developers,
I am having some trouble pushing to gerrit:
> clx72:qt $ git push gerrit HEAD:refs/for/4.8
> The authenticity of host 'outland.fnal.gov (131.225.135.249)' can't be
> established.
> RSA key fingerprint is a5:a4:7c:84:74:1e:a9:c6:b1:51:3a:be:13:d5:86:00.
> Are you sure you want to co
On quinta-feira, 24 de maio de 2012 12.03.28, Anttila Janne wrote:
> So what would be the correct approach?
> 1. Duplicate zlib to needed repos and try to keep different instances in
> sync (Like done currently)
> 2. Use exported zlib symbols from QtBase and
> include needed zlib header from QtBase
On quinta-feira, 24 de maio de 2012 11.46.05, Alberto Mardegan wrote:
> On 05/23/2012 02:43 PM, Thiago Macieira wrote:
> > My original solution was to have a parent only deref its children's shared
> > pointer counter, deleting it only if it became zero. That means that if
> > you
> > had a QShared
On quinta-feira, 24 de maio de 2012 12.13.31, Yan Shapochnik wrote:
> Since you are back porting this change to 4.8, I would also like to make a
> suggestion and include Mac OS X 10.8 Mountain Lion support in the same
> manner.
Yes, makes sense.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Since you are back porting this change to 4.8, I would also like to make a
suggestion and include Mac OS X 10.8 Mountain Lion support in the same manner.
Thanks,
Yan Shapochnik
-Original Message-
From: development-bounces+shapochniky=seapine@qt-project.org
[mailto:development-bounc
Hi,
Currently there are 3rdparty zlib sources in both qtbase and qtsvg
repositories, and in addition building zlib dependent imageformat plugins (mng,
tiff) are disabled in qtimageformats repo if platform does not have system zlib
available.
Already now zlib sources in qtbase and qtsvg have div
On quinta-feira, 24 de maio de 2012 13.10.23, Sergio Ahumada wrote:
> - for all projects ?
> - for some projects as a pilot ? which projects ?
> - for a dummy project so people can test it before going live ?
I'd like to see it in qtbase, but I figure that we should enable it at least
for all proj
[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 new enum in a patch level
> release. The only thing i
On 03/30/2012 09:41 AM, ext Sergio Ahumada wrote:
>>
>> We *really* need the topic branch reviewing feature back in. It's no fun
>> staging 19, 20, 20 and 21 changes...
>>
>
> We've fixed some of the problems with the topic branch feature and I'd
> like to enable it [1] again after our next release
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/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 Tue, May 22, 2012 at 2:07 PM, Thiago Macieira
wrote:
> There is no need for nominating for contribution. Anyone can contribute. Being
> a maintainer of something is what requires dedication.
>
> Unfortunately, for all sysadmin-related jobs, we have legal issues that need
> to be dealt with, so
Hello,
I would like to nominate Venugopal Shivashankar for approver status.
He has worked on Qt examples in Qt 4 and he is one of the prime editors in the
documentation team. He hasn't done many pushes
(https://codereview.qt-project.org/#q,owner:veshivas,n,z), but his
contributions are mostly
On 05/23/2012 02:43 PM, Thiago Macieira wrote:
> My original solution was to have a parent only deref its children's shared
> pointer counter, deleting it only if it became zero. That means that if you
> had a QSharedPointer to an object in the middle of the hierarchy, that object
> would be orp
On quarta-feira, 23 de maio de 2012 23.54.18, Girish Ramakrishnan wrote:
> Many of the boards come with very specific rootfs/linux. It's hard to
> install stuff on them. udev support is either there or not there. That
> doesn't mean you cannot plug devices into them, you can. Just that
> udev isn't
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 people scratching their heads, "but I have
Windows 8!" :-)
The
Moi,
Installer will ask the target dir while installing. By default is suggesting
/home/user/QtSDK.
I do imagine that you should be able to install those in parallel. Just make
sure that the paths are pointing to correct version while running.
Simo
On May 24, 2012, at 11:18 AM, ext Daniel Kreut
Regarding the input plugins: Once you reach a certain level of
complexity (that is, you need tighter integration between the input
subsystems and graphics, need device-specific workarounds, need to
support special embedded setups, etc.), you will find it easier and more
productive to simply fo
Hi,
On Thu, May 24, 2012 at 7:51 AM, wrote:
> Hi,
> Finally there is some progress with the bin packaging.
> There is now jenkins creating desktop installers twice a day, if there is
> change in git. Currently it detects the git 7 am and pm (GMT +2).
> First it creates the beta src package
> (
Hello,
On 23. mai 2012, at 20.12, ext Andreas Holzammer wrote:
Hi,
I wanted to backport the support for Windows 8 to Qt 4.8, which is
already done for Qt5 in https://codereview.qt-project.org/#change,22940
With this change a symbol is added and therefore binary compatibility is
broken. I know i
On Wed, May 23, 2012 at 11:54:18PM -0700, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
> > I think we should focus on keeping eglfs as small as possible, but
> > keeping the readability of the code, so that the entry level for "extending"
> > eglfs
On Thu, May 24, 2012 at 9:09 AM, Stephen Kelly wrote:
> I also prefer not adding backward source incompatible changes to Qt 4.8. Is
> there any precedent for doing it though? Do we know for sure whether it is
> binary incompatible or not to add an enum value?
AFAIK It's binary compatible, unless
On 24.05.2012 00:41, Girish Ramakrishnan wrote:
> On Wed, May 23, 2012 at 2:00 PM, Giuseppe D'Angelo wrote:
>
>> On 23 May 2012 20:03, Girish Ramakrishnan wrote:
>>
>>> Hi Andreas, On Wed, May 23, 2012 at 11:12 AM, Andreas Holzammer
>>> wrote:
>>>
Hi, I wanted to backport the support for Wind
51 matches
Mail list logo
