Hi,

I've been implementing custom components that should conform to the
qt-components API (QTCOMPONENTS-200). My post concerns segmented button
in a ButtonRow /ButtonColumn. I've understood the API so that if the
ButtonRow contains only Button components they are drawn as a segmented
button. Furthermore, my understanding is that if this kind of a
segmented ButtonRow is marked exclusive, there should always be one
button checked.

I noticed that the API tests for ButtonRow and ButtonColumn have the
following test:
- If ButtonRow is marked exclusive the checkable property of all buttons
must be true

In my opinion, this is in conflict with the above assumption of how
segmented button is assumed to work: in case of segmented button the
checked button should not be checkable, because at least one button must
be checked at a time and user is not allowed to uncheck all buttons.

Have you understood segmented button functionality similarly?

Br,
- Aki Kemppainen


-----Original Message-----
From: qt-components-bounces+aki.kemppainen=sasken....@qt.nokia.com
[mailto:qt-components-bounces+aki.kemppainen=sasken....@qt.nokia.com] On
Behalf Of qt-components-requ...@qt.nokia.com
Sent: 20. tammikuuta 2011 16:39
To: qt-components@qt.nokia.com
Subject: Qt-components Digest, Vol 2, Issue 17

Send Qt-components mailing list submissions to
        qt-components@qt.nokia.com

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.qt.nokia.com/mailman/listinfo/qt-components
or, via email, send a message with subject or body 'help' to
        qt-components-requ...@qt.nokia.com

You can reach the person managing the list at
        qt-components-ow...@qt.nokia.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Qt-components digest..."


Today's Topics:

   1. Re: Auto tests to verify common API (Artur Souza (MoRpHeUz))
   2. Re: Auto tests to verify common API (timo.rouvi...@nokia.com)
   3. Re: Auto tests to verify common API (Artur Souza (MoRpHeUz))
   4. Re: Auto tests to verify common API
      (Mikola Tapani (Nokia-MS/Tampere))
   5. Re: Auto tests to verify common API (J-P Nurmi)
   6. Re: Auto tests to verify common API (mika.juop...@nokia.com)
   7. Re: Auto tests to verify common API (Artur Souza (MoRpHeUz))


----------------------------------------------------------------------

Message: 1
Date: Thu, 20 Jan 2011 08:34:04 -0300
From: "Artur Souza (MoRpHeUz)" <artur.so...@openbossa.org>
Subject: Re: [Qt-components] Auto tests to verify common API
To: jari-pekka.nu...@nokia.com
Cc: qt-components@qt.nokia.com
Message-ID:
        <AANLkTinAV2RytHTdaH-X0XMCPZnVX9c1Szx=85aw6...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Hi!

On Thu, Jan 20, 2011 at 6:20 AM,  <jari-pekka.nu...@nokia.com> wrote:
> What's up with "tests/apicheck" and "tests/auto/api_*"? Is there a
plan to move to a direction or another? Or guys just weren't aware of
each others' work?

The idea behind apicheck is to validate a given module against the
common API. We are going to change the tests inside "tests/auto/api_*"
to be functional tests.

With tests/apicheck, any "components developer"
(meego/symbian/common/etc..) can run the tool against it's components
to check if they are following the common API :)

Cheers,

--
-------------------------------------------------------
Artur Duque de Souza
openBossa
INdT - Instituto Nokia de Tecnologia
-------------------------------------------------------
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------------------


------------------------------

Message: 2
Date: Thu, 20 Jan 2011 12:01:41 +0000
From: <timo.rouvi...@nokia.com>
Subject: Re: [Qt-components] Auto tests to verify common API
To: <artur.so...@openbossa.org>, <jari-pekka.nu...@nokia.com>
Cc: qt-components@qt.nokia.com
Message-ID:

<972362E7E1666049ABB32849B55904B30A3FD34B@008-AM1MPN1-004.mgdnok.nokia.c
om>

Content-Type: text/plain; charset="us-ascii"

>The idea behind apicheck is to validate a given module against the
>common API. We are going to change the tests inside "tests/auto/api_*"
>to be functional tests.

So does this mean that there will be:

Tests/auto/symbian
Tests/auto/meego
Tests/auto/mx

Etc.. so may the tests test something that's platform specific?

And then apicheck tests are completely cross-platform?

Br,
Timo

-----Original Message-----
From: qt-components-bounces+timo.rouvinen=nokia....@qt.nokia.com
[mailto:qt-components-bounces+timo.rouvinen=nokia....@qt.nokia.com] On
Behalf Of ext Artur Souza (MoRpHeUz)
Sent: 20.01.2011 13:34
To: Nurmi Jari-Pekka (Nokia-MS-Qt/Tampere)
Cc: qt-components@qt.nokia.com
Subject: Re: [Qt-components] Auto tests to verify common API

Hi!

On Thu, Jan 20, 2011 at 6:20 AM,  <jari-pekka.nu...@nokia.com> wrote:
> What's up with "tests/apicheck" and "tests/auto/api_*"? Is there a
plan to move to a direction or another? Or guys just weren't aware of
each others' work?

The idea behind apicheck is to validate a given module against the
common API. We are going to change the tests inside "tests/auto/api_*"
to be functional tests.

With tests/apicheck, any "components developer"
(meego/symbian/common/etc..) can run the tool against it's components
to check if they are following the common API :)

Cheers,

--
-------------------------------------------------------
Artur Duque de Souza
openBossa
INdT - Instituto Nokia de Tecnologia
-------------------------------------------------------
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------------------
_______________________________________________
Qt-components mailing list
Qt-components@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-components


------------------------------

Message: 3
Date: Thu, 20 Jan 2011 09:11:26 -0300
From: "Artur Souza (MoRpHeUz)" <artur.so...@openbossa.org>
Subject: Re: [Qt-components] Auto tests to verify common API
To: timo.rouvi...@nokia.com
Cc: qt-components@qt.nokia.com
Message-ID:
        <aanlktinnr9jv6y7d8mkt_cn0aszmokc6yjizlyhey...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 20, 2011 at 9:01 AM,  <timo.rouvi...@nokia.com> wrote:
>>The idea behind apicheck is to validate a given module against the
>>common API. We are going to change the tests inside "tests/auto/api_*"
>>to be functional tests.
>
> So does this mean that there will be:
>
> Tests/auto/symbian
> Tests/auto/meego
> Tests/auto/mx
>
> Etc.. so may the tests test something that's platform specific?

To be honest I didn't think about it but we could make it. I'll
discuss this with the team today. I'm assuming that it won't be an
issue for the CI system.

> And then apicheck tests are completely cross-platform?

Yes, as they only check for compatibility with the Common API and it
doesn't make functionality checks.

Cheers,

--
-------------------------------------------------------
Artur Duque de Souza
openBossa
INdT - Instituto Nokia de Tecnologia
-------------------------------------------------------
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------------------


------------------------------

Message: 4
Date: Thu, 20 Jan 2011 14:48:56 +0200
From: "Mikola Tapani (Nokia-MS/Tampere)" <tapani.mik...@nokia.com>
Subject: Re: [Qt-components] Auto tests to verify common API
To: "ext Artur Souza (MoRpHeUz)" <artur.so...@openbossa.org>
Cc: "qt-components@qt.nokia.com" <qt-components@qt.nokia.com>,
        "Rouvinen Timo \(Nokia-MS-Qt/Tampere\)"
<timo.rouvi...@nokia.com>
Message-ID: <4d382f38.80...@nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

But it would be possible to do cross platform functionality checks also?
Using import Qt.labs.components.native and then using only the Common
API

That would be good to avoid overlapping code under tests/auto

- Tapani

On 20/01/11 14:11, ext Artur Souza (MoRpHeUz) wrote:
> On Thu, Jan 20, 2011 at 9:01 AM,<timo.rouvi...@nokia.com>  wrote:
>>> The idea behind apicheck is to validate a given module against the
>>> common API. We are going to change the tests inside
"tests/auto/api_*"
>>> to be functional tests.
>>
>> So does this mean that there will be:
>>
>> Tests/auto/symbian
>> Tests/auto/meego
>> Tests/auto/mx
>>
>> Etc.. so may the tests test something that's platform specific?
>
> To be honest I didn't think about it but we could make it. I'll
> discuss this with the team today. I'm assuming that it won't be an
> issue for the CI system.
>
>> And then apicheck tests are completely cross-platform?
>
> Yes, as they only check for compatibility with the Common API and it
> doesn't make functionality checks.
>
> Cheers,
>


------------------------------

Message: 5
Date: Thu, 20 Jan 2011 15:12:33 +0200
From: J-P Nurmi <jpnu...@gmail.com>
Subject: Re: [Qt-components] Auto tests to verify common API
To: qt-components@qt.nokia.com
Message-ID:
        <AANLkTinVBGkzdD0yKr6eVZ+61=mxwbaeese8un0t1...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 20, 2011 at 2:48 PM, Mikola Tapani (Nokia-MS/Tampere)
<tapani.mik...@nokia.com> wrote:
> But it would be possible to do cross platform functionality checks
also?
> Using import Qt.labs.components.native and then using only the Common
API
>
> That would be good to avoid overlapping code under tests/auto

Hi all,

There's a MR to enable local 'make check' for auto tests that import
native components. With "local" I mean that it doesn't depend on 'make
install'. Currently we put native imports in place only in the install
step. Please take a look, it's getting so complex that it wouldn't
heart to have several pairs of eye balls reviewing it...

http://qt.gitorious.org/qt-components/qt-components/merge_requests/146

--
J-P Nurmi


------------------------------

Message: 6
Date: Thu, 20 Jan 2011 13:34:33 +0000
From: <mika.juop...@nokia.com>
Subject: Re: [Qt-components] Auto tests to verify common API
To: <tapani.mik...@nokia.com>, <artur.so...@openbossa.org>
Cc: qt-components@qt.nokia.com, timo.rouvi...@nokia.com
Message-ID:

<1756B2D84AE76441A4385678FB86FC2B0725F6E0@008-AM1MPN1-026.mgdnok.nokia.c
om>

Content-Type: text/plain; charset="us-ascii"

So should we put cross platform functionality check under
tests/auto/native folder? And all the other functionality than what is
in common API are in their own folders (like Timo wrote below).

T.Mika


-----Original Message-----
From: qt-components-bounces+mika.juoperi=nokia....@qt.nokia.com
[mailto:qt-components-bounces+mika.juoperi=nokia....@qt.nokia.com] On
Behalf Of Mikola Tapani (Nokia-MS/Tampere)
Sent: 20. tammikuuta 2011 14:49
To: ext Artur Souza (MoRpHeUz)
Cc: qt-components@qt.nokia.com; Rouvinen Timo (Nokia-MS-Qt/Tampere)
Subject: Re: [Qt-components] Auto tests to verify common API

But it would be possible to do cross platform functionality checks also?
Using import Qt.labs.components.native and then using only the Common
API

That would be good to avoid overlapping code under tests/auto

- Tapani

On 20/01/11 14:11, ext Artur Souza (MoRpHeUz) wrote:
> On Thu, Jan 20, 2011 at 9:01 AM,<timo.rouvi...@nokia.com>  wrote:
>>> The idea behind apicheck is to validate a given module against the
>>> common API. We are going to change the tests inside
"tests/auto/api_*"
>>> to be functional tests.
>>
>> So does this mean that there will be:
>>
>> Tests/auto/symbian
>> Tests/auto/meego
>> Tests/auto/mx
>>
>> Etc.. so may the tests test something that's platform specific?
>
> To be honest I didn't think about it but we could make it. I'll
> discuss this with the team today. I'm assuming that it won't be an
> issue for the CI system.
>
>> And then apicheck tests are completely cross-platform?
>
> Yes, as they only check for compatibility with the Common API and it
> doesn't make functionality checks.
>
> Cheers,
>
_______________________________________________
Qt-components mailing list
Qt-components@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-components


------------------------------

Message: 7
Date: Thu, 20 Jan 2011 11:39:07 -0300
From: "Artur Souza (MoRpHeUz)" <artur.so...@openbossa.org>
Subject: Re: [Qt-components] Auto tests to verify common API
To: "Mikola Tapani (Nokia-MS/Tampere)" <tapani.mik...@nokia.com>
Cc: "qt-components@qt.nokia.com" <qt-components@qt.nokia.com>,
        "Rouvinen Timo \(Nokia-MS-Qt/Tampere\)"
<timo.rouvi...@nokia.com>
Message-ID:
        <AANLkTik4=22L_eB+n5qykHMM9SsawWP+0Ci=0evow...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 20, 2011 at 9:48 AM, Mikola Tapani (Nokia-MS/Tampere)
<tapani.mik...@nokia.com> wrote:
> But it would be possible to do cross platform functionality checks
also?
> Using import Qt.labs.components.native and then using only the Common
API
>
> That would be good to avoid overlapping code under tests/auto

That's exactly our idea. We will fix all the auto tests regarding the
common api functionality now :)

Cheers,

--
-------------------------------------------------------
Artur Duque de Souza
openBossa
INdT - Instituto Nokia de Tecnologia
-------------------------------------------------------
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------------------


------------------------------

_______________________________________________
Qt-components mailing list
Qt-components@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-components


End of Qt-components Digest, Vol 2, Issue 17
********************************************

SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary 
or legally privileged information. In case you are not the original intended 
Recipient of the message, you must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message and you are requested to 
delete it and inform the sender. Any views expressed in this message are those 
of the individual sender unless otherwise stated. Nothing contained in this 
message shall be construed as an offer or acceptance of any offer by Sasken 
Communication Technologies Limited ("Sasken") unless sent with that express 
intent and with due authority of Sasken. Sasken has taken enough precautions to 
prevent the spread of viruses. However the company accepts no liability for any 
damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
_______________________________________________
Qt-components mailing list
Qt-components@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-components

Reply via email to