On Mar 11, 2013, at 12:41 PM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
By the way, I don't know if you saw my comments on your Qt for iOS Preview
blog post, but...
You stated that because there is no HITheme-like API on iOS, that creating
QiOSStyle would be not
Hi
We had problems with Linuces and perhaps Macs since last Thursday up until
yesterday (11.mar) noon. Puppet runs got stuck and took up all of the free CPU
power. Puppet was fixed, but the situation got fixed only after each server
re-ran Puppet AND rebooted so that the Puppet's that were
On Tue, Mar 12, 2013 at 04:35:59AM +0100, Axel Waggershauser wrote:
So to fix whitespace (according to
http://qt-project.org/wiki/Qt_Coding_Style) one has to come up with
whitespace-only patches. I have a couple of questions regarding those:
1. Is something like the above patch welcome at
On Tue, Mar 12, 2013 at 07:56:33AM +, Bache-Wiig Jens wrote:
On Mar 11, 2013, at 12:41 PM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
By the way, I don't know if you saw my comments on your Qt for iOS
Preview blog post, but...
You stated that because there is no
I agree 100% with Jens. That is all.
tor arne
On 3/12/13 8:56 , Bache-Wiig Jens wrote:
[snip]
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
3. How to best split up patches from that category? e.g. fixing all
if(...){ - if (...) { occurrences in qtbase would be a rather
large patch (I have it half done)
a) split that up based on manageable subdirectories?
yes, and that only for easy recovery from merge conflicts (which you
Hi, there is any way to add recording support to QMediaPlayer?, I was reading
the code of qmediaplayer.cpp from Qt5 sources and realize that there's not
support:
QMediaServiceProvider *provider =
QMediaServiceProvider::defaultServiceProvider();
if (flags) {
Axel sayeth:
snip, whitespace-only changes for consistency to
coding standard
+1 YAY, Axel!
This is a personal wish by me -- consistency. Including for whitespace.
I find it astounding the legacy-code-bases that essentially decide that
they cannot be improved -- no such patches are
On Mar 11, 2013, at 2:44 PM, Frank Osterfeld frank.osterf...@kdab.com wrote:
Hi,
I see two ways to fix it, one is a one-liner, one's more work:
* Don't silently accept touch events if no item is waiting for them.
Ignoring the events triggers the touch-mouse fallback. That's the approach
On Tue, Mar 12, 2013 at 01:34:54PM +0100, Axel Waggershauser wrote:
I thought splitting by type first and potentially by directory second
if it is too big still, would be best because it reduces the burden on
the reviewer: only one type of change should be easier to skim over
the downside of
Hello,
I want to express another suggestions for bug management:
- A newly opened bug report shouldn't be automatically assigned to anyone.
- Logged-in users should be able to assign bug reports to themselves.
Assigned = 'someone works or is going to work on the item'
Unassigned = 'nobody works
On 03/03/2013 01:23 AM, Rohan McGovern wrote:
On Sat, Mar 2, 2013 at 3:34 PM, Laszlo Papp lp...@kde.org wrote:
I will take you meant QT_MODULE_TO_TEST=qtdeclarative
qtqa/tests/prebuild/license/tst_licenses.pl
Yeah, I used this script earlier, but I did not know it is already
integrated into
Hello,
After a few discussions, I want to suggest that we could make JIRA more
accessible so that every logged-in user should have rights to:
- create,
- edit,
- resolve,
- verify,
- and re-open bug reports.
Please feel free to comment on this.
If there are no serious objections, this change
Hello,
I want to suggest another change for JIRA:
- A Reporter should be able to set the Priority starting from the Create Issue
window.
- Guidelines for setting Priority should be provided (already working today).
Please feel free to comment on this.
If there are no serious objections, this
I would expect that the workflow is that if a report is set to be In progress
then this is the indication that someone is actually working on the report, if
we start using the assigner for this indication then it sounds like it will
complicate matters even further. Also, if a P1 is created and
On 01/24/2013 08:49 AM, Jenssen Tim wrote:
Another big +2
Von: Sergio Ahumada mailto:sergio.ahum...@digia.com
Gesendet: 23.01.2013 14:27
An: development@qt-project.org mailto:development@qt-project.org
Betreff:
On Tue, Mar 12, 2013 at 2:11 PM, Oswald Buddenhagen
oswald.buddenha...@digia.com wrote:
On Tue, Mar 12, 2013 at 01:34:54PM +0100, Axel Waggershauser wrote:
I thought splitting by type first and potentially by directory second
if it is too big still, would be best because it reduces the burden
On Mar 12, 2013, at 2:01 PM, Sorvig Morten wrote:
On Mar 11, 2013, at 2:44 PM, Frank Osterfeld frank.osterf...@kdab.com wrote:
Hi,
I see two ways to fix it, one is a one-liner, one's more work:
* Don't silently accept touch events if no item is waiting for them.
Ignoring the events
On 03/01/2013 10:28 AM, Hirvonen Olli wrote:
Hi all,
We would appreciate Your help in one quite trivial task. With a joint
effort together it also should be reasonable small task for individual
developer. Digia acquired all Nokia's Qt copyrights last year. We have
already changed the
On Wednesday, March 06, 2013 09:43:12 Motyka Rafal wrote:
Hello,
This is a request for help to update/correct the new Sanity Test Guidelines
page. Please feel free to change the page:
http://qt-project.org/wiki/Sanity-Test-Guidelines It's meant to be used for
Qt releases as help for manual
On 02/06/2013 07:25 PM, Olivier Goffart wrote:
On Thursday 31 January 2013 07:50:32 Koehne Kai wrote:
-Original Message-
From: development-bounces+kai.koehne=digia@qt-project.org
[mailto:development-bounces+kai.koehne=digia@qt-project.org] On
Behalf Of Matt Williams
Sent:
On Tue, Mar 12, 2013 at 03:14:43PM +0100, Axel Waggershauser wrote:
On Tue, Mar 12, 2013 at 2:11 PM, Oswald Buddenhagen
oswald.buddenha...@digia.com wrote:
if the burden on the reviewer is too big, then you didn't split it up
according to directories/modules sufficiently well.
What would
On Tue, Mar 12, 2013 at 01:28:37PM +, Motyka Rafal wrote:
Hello,
I want to suggest another change for JIRA:
- A Reporter should be able to set the Priority starting from the Create
Issue window.
i don't think so. seriously, everyone thinks that their issue is the
most important one.
On terça-feira, 12 de março de 2013 13.28.37, Motyka Rafal wrote:
Hello,
I want to suggest another change for JIRA:
- A Reporter should be able to set the Priority starting from the Create
Issue window.
- Guidelines for setting Priority should be provided (already
working today).
Please
On terça-feira, 12 de março de 2013 13.41.33, Shaw Andy wrote:
I would expect that the workflow is that if a report is set to be In
progress then this is the indication that someone is actually working on
the report, if we start using the assigner for this indication then it
sounds like it
2013/3/12 Oswald Buddenhagen oswald.buddenha...@digia.com:
somebody attempted this just a few days ago, but gave up when the scope
of the undertaking became clear. i can't find the change now ...
https://codereview.qt-project.org/#change,48150
I indeed gave up, or at least I was trying to
I'm already working on some preliminary testing for QIosStyle. I don't know how
long it'll be before I have something on Gerrit but it will come.
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petrou...@petroules.com
On Mar 12, 2013, at 7:52 AM,
2013/3/12 Sergey Belyashov sergey.belyas...@gmail.com:
Laszlo is not primary maintainer. But Denis is. Laszlo is most active
developer.
Our policy is to accept features if only all 3 maintainers accepts it. I an
Denis can accept your change. If you persuade Laszlo to accept patch then it
will
On Tue, Mar 12, 2013 at 5:32 PM, Oswald Buddenhagen
oswald.buddenha...@digia.com wrote:
it went to the trash because the idea was not liked back then. the winds
appear to have changed meanwhile.
That is a pitty. Given, that I already spent a bunch of hours looking
into this, I hope you are
29 matches
Mail list logo
