On 14/01/2014 08:26, Oliver Wolff wrote:
Hi,
I am trying to fix
https://bugreports.qt-project.org/browse/QTBUG-35632 and while
doing so I noticed that this use case is broken on Linux, Windows and
Mac. Running
the code from my last comment I get different results depending on the
platform. W
Hi,
I am trying to fix https://bugreports.qt-project.org/browse/QTBUG-35632
and while
doing so I noticed that this use case is broken on Linux, Windows and
Mac. Running
the code from my last comment I get different results depending on the
platform. When
it is run on Linux or Windows I get:
E
Hi,
All merges are now done, so all changes required for Qt 5.2.1 need
to be pushed to the 'release' branch from now on.
Only changes fixing P0 or P1 (and really important P2) can be pushed
directly to the release branch.
Changes in the release branch need to be reviewed as usual, but only the
On 14/01/14 06:10, Hausmann Simon wrote:
>
> I use personal name spaces on gerrit frequently, works great for me.
>
then everything is there to configure and use this feature
http://gerrit.googlecode.com/svn/documentation/2.2.1/access-control.html#_project_access_control_lists
__
I use personal name spaces on gerrit frequently, works great for me.
Simon
Fra: Thiago Macieira
Sendt: 00:16 tirsdag 14. januar 2014
Til: development@qt-project.org
Emne: Re: [Development] FYI: personal namspaces available on gerrit, aka where
to put backups
On segunda-feira, 13 de janeiro de
In the Image Formats part of QImage doc says
"
The allGray() and isGrayscale() functions tell whether a color image can safely
be converted to a grayscale image.
"
but in the doc of there 2 functions indicate they're used to decide whether an
image is grayscale image ,not mentioned they could be
On segunda-feira, 13 de janeiro de 2014 23:57:52, Sergio Ahumada wrote:
> http://code.google.com/p/gerrit/issues/detail?id=1008
>
> but as far as I know, the above refs/personal/$user/ never worked well
> for us (or at least I am not aware of anybody using it atm)
I did one push there.
--
Thiag
On 13/01/14 23:39, Thiago Macieira wrote:
> On sexta-feira, 15 de fevereiro de 2013 16:28:02, Oswald Buddenhagen wrote:
>> moin,
>>
>> another one from the "could have done this much earlier" ...
>>
>> everyone has a personal namespace under refs/personal/$user/ in every
>> repository hosted on our
On sexta-feira, 15 de fevereiro de 2013 16:28:02, Oswald Buddenhagen wrote:
> moin,
>
> another one from the "could have done this much earlier" ...
>
> everyone has a personal namespace under refs/personal/$user/ in every
> repository hosted on our gerrit. it's possible to create arbitrary
> bra
On segunda-feira, 13 de janeiro de 2014 21:48:22, Kevin Krammer wrote:
> The alternative to platform plugins is to put all those IPC basics into
> QtCore itself, like what was done for PPS. I.e. moving parts of QtDBus
> into QtCore.
We could do that, though I'd rather not. The basics for kdbus wi
The following changes have been unreviewed for some time, even after my ping
of 10 days ago:
https://codereview.qt-project.org/73060 Centralize support for QBasicAtomic
for ints and longs
https://codereview.qt-project.org/73062 Replace the type-based
QAtomicIntegerTraits with a size-based one
h
On Monday, 2014-01-13, 12:37:54, Thiago Macieira wrote:
> On segunda-feira, 13 de janeiro de 2014 21:28:05, Kevin Krammer wrote:
> > D-Bus simply is *the* system integration technology on Linux, QtCore will
> > need to be able to do D-Bus at runtime.
>
> That will always require plugins.
Yes, bu
On segunda-feira, 13 de janeiro de 2014 21:28:05, Kevin Krammer wrote:
> D-Bus simply is *the* system integration technology on Linux, QtCore will
> need to be able to do D-Bus at runtime.
That will always require plugins.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
On Monday, 2014-01-13, 22:00:53, abba...@gmail.com wrote:
> 1) well, it can go to qt base, but what module? We can't add mount and
> monitor to qtcore, because Linux implementation will require dbus.
I think this will come up again and again until there is a QPA like platform
adapter on the QtCo
Hello,
I understand that Widgets are considered "complete" in Qt5, and no new
features are going to be added, but it's seeming more and more like the
actual position of developers is that Widgets are fully deprecated.
For at least five months Digia and others have known that one of the
fundamenta
2014/1/13 David Faure
> On Monday, January 13, 2014 10:32:12 PM abba...@gmail.com wrote:
> > I think, "mount" requires root privileges, doesn't it?
>
> Not if the entry is present in fstab, with the option user or users.
>
>
Still, what about volumes (|un)mounting of which requires higher privile
On 2014-01-13, David Faure wrote:
> Mounting can still be done with `mount`, no?
Only in rare cases. Normally on linux from a user app you would call out
to udisks, who would connect to polkit and have polkit maybe query you
and other magic.
> Notifications mean listening to dbus signals though,
On Monday, January 13, 2014 10:32:12 PM abba...@gmail.com wrote:
> I think, "mount" requires root privileges, doesn't it?
Not if the entry is present in fstab, with the option user or users.
--
David Faure | david.fa...@kdab.com | Managing Director KDAB France
KDAB (France) S.A.S., a KDAB Group
I think, "mount" requires root privileges, doesn't it?
Not sure about libudev, maybe it can be used from userspace...
Иван Комиссаров
> 13 янв. 2014 г., в 22:17, David Faure написал(а):
>
> On Monday 13 January 2014 18:04:24 Tony Van Eerd wrote:
>>> 1) well, it can go to qt base, but what modu
On Monday 13 January 2014 18:04:24 Tony Van Eerd wrote:
> > 1) well, it can go to qt base, but what module? We can't add mount and
> > monitor to qtcore, because Linux implementation will require dbus.
>
> I'm not familiar with the details there, can you briefly explain why dbus is
> necessary and
On segunda-feira, 13 de janeiro de 2014 18:04:24, Tony Van Eerd wrote:
> > 1) well, it can go to qt base, but what module? We can't add mount and
> > monitor to qtcore, because Linux implementation will require dbus.
>
> I'm not familiar with the details there, can you briefly explain why dbus is
>
> 1) well, it can go to qt base, but what module? We can't add mount and
> monitor to qtcore, because Linux implementation will require dbus.
I'm not familiar with the details there, can you briefly explain why dbus is
necessary and why it is a bad thing for qtcore?
> 2) separate, see above.
1) well, it can go to qt base, but what module? We can't add mount and monitor
to qtcore, because Linux implementation will require dbus.
2) separate, see above. Drive info should belong to qt core, IMHO.
Иван Комиссаров
13 янв. 2014 г., в 21:53, Tony Van Eerd написал(а):
>>
>>> On 13 Jan 201
>
> On 13 Jan 2014, at 5:06 PM, Alvin Yulo wrote:
>
> > Here are the QDrive APIs that Tony mentioned below:
> > https://codereview.qt-project.org/#change,75336,patchset=1
>
> Cool.
>
> But I think maybe we should get the C++ APIs into qtbase, so that
> QtQuick.Controls.FileDialog doesn't depend
On 13 Jan 2014, at 5:06 PM, Alvin Yulo wrote:
> Here are the QDrive APIs that Tony mentioned below:
> https://codereview.qt-project.org/#change,75336,patchset=1
Cool.
But I think maybe we should get the C++ APIs into qtbase, so that
QtQuick.Controls.FileDialog doesn't depend on qtsystems. So
Hi everybody,
We are two students currently working on a research project regarding
motivation for contributing to Open Source projects. You can help us by filling
out the following web-survey, it only takes max. 2 minutes!
This is the link: http://goo.gl/5bwR9t
Thanks!
___
I had some changes but unit tests are failing with
FAIL! : tst_QTcpServer::linkLocal(WithoutProxy)
'socket->waitForConnected(5000)' returned FALSE. ()
Loc: [../tst_qtcpserver.cpp(929)]
Is there a problem with the test servers?
see: https://codereview.qt-project.org/#change,73476 and
https:
Hi,
a long time ago Marius Storm-Olsen wrote a nice convenience tool to ease
pushing to gerrit. As probably most are unaware of that tool, I'll just resend
his original annoucement.
--
Hi,
I've just pushed a convenience script to the qtrepotools repository,
which makes it easier to push p
This issue is valid since Qt 5.0.0... More details in
https://bugreports.qt-project.org/browse/QTBUG-31724
My "temporary" solution is build my qt libs with "-developer -debug
-no-framework", it works fine both with creator and xcode.
Regards,
Liang
From:
On Jan 12, 2014, at 7:16 AM, Mike Krus wrote:
> as far as I know, debug builds on OSX are not redistributable because they
> directly reference the location of the source files.
> So you need to do your own build and keep the source files in the same place.
Both gdb and lldb offers a way of sub
On Monday 30 December 2013 19:26:58 Thiago Macieira wrote:
> On segunda-feira, 30 de dezembro de 2013 21:20:06, David Faure wrote:
> > Xlib.h is included by
> > src/3rdparty/angle/include/EGL/eglplatform.h
> >
> > I do have /usr/include/EGL/egl.h btw.
>
> What provides it?
Mesa-libEGL-devel-9.0
Hi,
Just a reminder: stable->release merge is ongoing. Still waiting for last
staged changed to be integrated, and after that we can proceed with the merge.
There seems to be some changes in stable which are not staged, so those changes
has to be submitted into release -branch if change needs to
Hi all,
We are planning to have Qt 5.2.1 release pretty soon. Merge from stable to
release is planned to be done today (as Matti informed about week ago, see
http://lists.qt-project.org/pipermail/development/2014-January/014882.html )
and release will be done soon after that. Target is to get R
On Jan 11, 2014, at 5:55 AM, Kuba Ober wrote:
> On Jan 10, 2014, at 6:07 AM, Ziller Eike wrote:
>
>> On Jan 9, 2014, at 6:05 PM, Kuba Ober wrote:
>>
>>> I’m trying to figure out the most constructive way of ensuring that an OS X
>>> build of Qt, installed with the source code, can be actual
34 matches
Mail list logo
