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 04/13/2012 08:41 PM, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Fri, Apr 13, 2012 at 11:30 AM, Girish Ramakrishnan
> wrote:
>
>> I think the idea with _qpa_ in the file name is to imply that it has
>> plugin api. As opposed to let's say qpen_p.h. This means that when I
>> see a change to a _
On sexta-feira, 13 de abril de 2012 11.30.42, Girish Ramakrishnan wrote:
> Yes, agreed (and thanks for those pragmas that I was not aware of).
Remember to wrap them in #if 0, so only syncqt will see them.
> I think the idea with _qpa_ in the file name is to imply that it has
> plugin api. As oppo
Hi,
On Fri, Apr 13, 2012 at 11:30 AM, Girish Ramakrishnan
wrote:
> I think the idea with _qpa_ in the file name is to imply that it has
> plugin api. As opposed to let's say qpen_p.h. This means that when I
> see a change to a _qpa.h file, I know that plugins will get affected
> by this api chan
Hi Thiago,
2012/4/13 Thiago Macieira :
> On sexta-feira, 13 de abril de 2012 11.03.58, Girish Ramakrishnan wrote:
>> Hi Thiago,
>> > Let's please not invent a new rule.
>> >
>> > If it's _p.h, it's private, otherwise it's public and subject to source-
>> > and binary-compatibility guarantees. If t
On sexta-feira, 13 de abril de 2012 11.03.58, Girish Ramakrishnan wrote:
> Hi Thiago,
> > Let's please not invent a new rule.
> >
> > If it's _p.h, it's private, otherwise it's public and subject to source-
> > and binary-compatibility guarantees. If there's API in some files that we
> > don't want
Hi Thiago,
2012/4/13 Thiago Macieira :
> On sexta-feira, 13 de abril de 2012 19.18.26, 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 submitti
On 04/12/2012 06:54 PM, ext quim@nokia.com wrote:
> Alright, forget all this. Let me arrive at home and change the wiki page.
>
>
> I will start by asking people to send me an email with those fields. Any
> improvement from that lowest point is welcome.
Alexandra has been kind enough to provid
On sexta-feira, 13 de abril de 2012 19.18.26, 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 Lar
On 04/13/2012 07:27 PM, ext Girish Ramakrishnan wrote:
> On Fri, Apr 13, 2012 at 10:18 AM, Samuel Rødal wrote:
>> On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>>> My current understanding of the "qpa" plan is this, correct me if I am
>>> wrong:
>>> 1. Files with _qpa in them are suppose
On Fri, Apr 13, 2012 at 10:18 AM, 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 ha
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 enough trouble as-is with
> getting api_changes to merge
I do propose that we freeze http://wiki.qt-project.org/ giving editing
permissions only to
http://wiki.qt-project.org/index.php?title=Special:ListUsers&group=sysop
and seting a deprecation period of 6? months. At the date agreed the
wiki would be switched off.
In the meantime the pages that ma
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 enough trouble as-is with
getting api_changes to merge to master :-) All the commits will have
the "api:" prefix in the
On sexta-feira, 13 de abril de 2012 13.41.34, Thiago Macieira wrote:
> I ran into Ossi and Marius S.O. talking about the mess we have with the
> build and use of Qt as shared/DLL or static. It's something I had begun
> fixing, but I haven't finished yet.
>
> If you're dealing with a different build
I ran into Ossi and Marius S.O. talking about the mess we have with the build
and use of Qt as shared/DLL or static. It's something I had begun fixing, but I
haven't finished yet.
If you're dealing with a different buildsystem than qmake, or you're packaging
Qt, please my email that is a reply to
On 13/04/2012 11:03, ext Girish Ramakrishnan wrote:
> On Fri, Apr 13, 2012 at 8:57 AM,
> wrote:
>> On 13/04/2012 08:50, ext Girish Ramakrishnan wrote:
>>> On Fri, Apr 13, 2012 at 1:56 AM,
>>> wrote: Will the old pages redirect to the new one or will the
>>> domain wiki.qt-project.org completely die
On Fri, Apr 13, 2012 at 3:20 AM, Samuel Rødal wrote:
> On 04/13/2012 11:37 AM, ext Hannu Lyytinen wrote:
>> Hello all,
>>
>> after doing some small fixes to KMS QPA plugin, I proceeded with
>> implementing the input device support via evdev. It was soon pointed out
>> that perhaps using the generi
On Fri, Apr 13, 2012 at 8:57 AM, wrote:
> On 13/04/2012 08:50, ext Girish Ramakrishnan wrote:
>> On Fri, Apr 13, 2012 at 1:56 AM, wrote:
>>> Starting from Thursday next week, we will copy the pages that
>>> currently live on wiki.qt-project.org over to qt-project.org/wiki,
>>> below the "Develop
On 13/04/2012 08:50, ext Girish Ramakrishnan wrote:
> On Fri, Apr 13, 2012 at 1:56 AM, wrote:
>> Starting from Thursday next week, we will copy the pages that
>> currently live on wiki.qt-project.org over to qt-project.org/wiki,
>> below the "Developing Qt" category. It's not the perfect way of
>>
Hi all,
When testing Qwt with Qt5 I was running a NX ( http://www.nomachine.com
) remote desktop. Local was a SuSE/Linux 11.2, remote ran a SuSE 12.1/Linux.
With about half of the Qwt applications I had the following effect: as
soon as I move the mouse over the application window ( Xfce4, focus
On 13/04/2012 09:41, ext jason.mcdon...@nokia.com wrote:
>> Random question of the day: do you happen to have stats about how
>> often those insignificant tests actually fail? That should help to
>> figure out which ones are actually working, and therefore should
>> not be marked as insignificant.
> Random question of the day: do you happen to have stats about how
> often those insignificant tests actually fail? That should help to
> figure out which ones are actually working, and therefore should not
> be marked as insignificant.
I'm glad you asked. I spent some time yesterday and today d
> Random question of the day: do you happen to have stats about how often
> those insignificant tests actually fail? That should help to figure out
> which ones are actually working, and therefore should not be marked as
> insignificant.
>
> --
> Giuseppe D'Angelo
The CI logs are publicly availabl
2012/4/13 :
>>
> Another way tests have been disabled is using CONFIG += no_check_target
> which seems to have been done when tests were initially disabled before the
> insignificant_test option was added.
Random question of the day: do you happen to have stats about how
often those insignificant
>Another way tests have been disabled is using CONFIG += no_check_target which
>seems to have been done when tests were initially disabled before the
>insignificant_test option was added.
Actually, I think that came a little later (when the refactor branch was merged
into master). That mechani
Hi Alexandra,
On Fri, Apr 13, 2012 at 1:56 AM, wrote:
> Hello!
>
> I assume everyone is aware of the current situation of us having two
> different wikis: one at wiki.qt-project.org and one at
> qt-project.org/wiki. It was never planned to happen that way, but
> sometimes plans don't really work
Another way tests have been disabled is using CONFIG += no_check_target which
seems to have been done when tests were initially disabled before the
insignificant_test option was added.
e.g. auto.pro has this:
# disable 'make check' on Mac OS X for the following subdirs for the time being
mac {
> I've grepped through all the modules to create a list of these insignificant
> tests, and listed them below. Please note that a test marked as insignificant
> in essence provides us with zero coverage, since all results from those test
> cases (although run) are completely ignored.
> IMO, if
On 04/13/2012 11:37 AM, ext Hannu Lyytinen wrote:
> Hello all,
>
> after doing some small fixes to KMS QPA plugin, I proceeded with
> implementing the input device support via evdev. It was soon pointed out
> that perhaps using the generic evdev plugins would be better idea. I
> experimented with
> -Original Message-
> From: Beck Wolfgang (Nokia-MP/Brisbane)
> Sent: Friday, April 13, 2012 1:23 AM
> To: Koehne Kai (Nokia-MP/Berlin); thiago.macie...@intel.com;
> development@qt-project.org
> Subject: RE: [Development] Proposed API change: Change signature of
> QMessageHandler to use QS
On Fri, 13 Apr 2012 02:30:08 ext Charley Bay wrote:
> >
> IMHO, it seems like this "theming" and "styling" thing should be so much
> *easier* with QML. But, I'm not seeing approaches (yet) on these lists
> that will work for us.
>
> This is not a complaint: The QML declarative paradigm is new,
Hello all,
after doing some small fixes to KMS QPA plugin, I proceeded with
implementing the input device support via evdev. It was soon pointed out
that perhaps using the generic evdev plugins would be better idea. I
experimented with them a bit and seems they need some work.
Specifically, all th
Hello!
I assume everyone is aware of the current situation of us having two
different wikis: one at wiki.qt-project.org and one at
qt-project.org/wiki. It was never planned to happen that way, but
sometimes plans don't really work out the way I think. :P
Anyway, the current situation is stupid, a
On 4/13/12 10:32 AM, "ext Oswald Buddenhagen"
wrote:
>On Fri, Apr 13, 2012 at 07:04:42AM +, ext
>casper.vandonde...@nokia.com wrote:
>> You are correct, that is what will happen, the same as the current
>>system.
>> The thing is that people have difficulty understanding where
>> QT_QML_QDOC
On Fri, Apr 13, 2012 at 07:04:42AM +, ext casper.vandonde...@nokia.com
wrote:
> You are correct, that is what will happen, the same as the current system.
> The thing is that people have difficulty understanding where
> QT_QML_QDOCCONF etc. come from currently.
>
> I can see a problem with th
On 4/13/12 7:34 AM, "Lincoln Ramsay" wrote:
>On 04/13/2012 03:19 PM, Vandonderen Casper (Nokia-MP/Oslo) wrote:
>> But I would be grateful if you would make a plan on how to turn qdoc
>> into a mini-qmake so that qdoc can parse the .pro/sync.profile, so
>> that we don't need the depends. Because t
37 matches
Mail list logo
