Re: [Development] Request for new Playground Repo

2013-11-21 Thread Vladimir Minenko
We actually have got a few more APIs which we would move to that
repository either right now, or later when it becomes an add-on. Some of
those APIs need to go under a review to sort our what would be the place
to put them in.

For now, we are asking for a home to start with.

Cheers!

--
Vladimir

On 20.11.13 23:47, André Pönitz
andre.poen...@mathematik.tu-chemnitz.de wrote:

On Wed, Nov 20, 2013 at 07:51:34PM +, Knoll Lars wrote:
 On 20/11/13 20:36, Andrew Wooster awoos...@blackberry.com wrote:
 
 Hi, I'd like to request the creation of a new playground repository.
 
 Name: BlackBerry Extras
 
 Description: A repository for creating BlackBerry specific APIs that
are
 useful for implementing Qt functionality.
 
 Let me know if there are any questions.
 
 If the purpose is the same as the other QPlatformExtras modules, I¹m
happy
 to add it.

I am not.

The general approach is wrong, for several reasons:

1. Splitting the platform extras already on the module level means that
everybody who wants to use some of the extras even buried behind #ifdef's
somewhere deep in his code has to add platform specific conditional code
like

   !isEmpty(QT.x11extras.name) {
QT += x11extras
DEFINES += I_CAN_USE_X11EXTRAS
} else {
warning(x11extras module not found, )
}

to his buildsystem(s), for each of the platforms he want to fully
support. This is a maintanance burden not just for the buildsystem itself
but also extends to conditional packaging/installation.

2. The setup is inherently fragile as only part of the code is used, and
part
not even checked on a specific developer's machine at a time, bearing the
risk of the classic compile fix or CI ping pong.

3. The approach does not scale as it does not offer a natural place for
features that are not available on all platforms, but on more then one.
Putting random sort-of-sharable code into qtbase is not a good alternative
either.


There is no perfect solution, but the further down the conditionals
are in the code the less impact they have on all three aspects, and
the more code can be shared between the backends.

Merging the platform into a single module with fat #ifdefs QT_OS_XYZ
in the headers would already alleviate the problem on the build system
level, and upwards (packaging...), while providing the same interface
to the actual code. That'd be a uniform improvemnt over the current setup.

Andre'
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-21 Thread Kevin Krammer
On Wednesday, 2013-11-20, 19:36:00, Andrew Wooster wrote:
 Hi, I'd like to request the creation of a new playground repository.
 
 Name: BlackBerry Extras
 
 Description: A repository for creating BlackBerry specific APIs that are
 useful for implementing Qt functionality.
 
 Let me know if there are any questions.

Since I saw PPS being mentioned as one of the extra APIs, isn't that also 
available on stock QNX?

I.e. would it make sense to follow the naming used for the QPA or is the plan 
to mostly add BB specific APIs?

Cheers,
Kevin

-- 
Kevin Krammer | kevin.kram...@kdab.com | Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions


smime.p7s
Description: S/MIME cryptographic signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-21 Thread Fabian Bumberger
Hi,

 so unless this is going to be a huge beast, maybe qtbase would be actually a 
 better target?
I agree that it would be much better to have it in QtBase, if this is possible. 
Above all, because certain parts there use PPS (e.g. QPA and Locale).
And it is not a huge beast (see 
https://qt.gitorious.org/qt/qtlocation/source/469cbf8f601270ac0b030202ae303939ba4c63ff:src/plugins/position/blackberry/bb)

Fabian

From: development-bounces+fbumberger=blackberry@qt-project.org 
[development-bounces+fbumberger=blackberry@qt-project.org] on behalf of 
Kevin Krammer [kevin.kram...@kdab.com]
Sent: Thursday, November 21, 2013 10:03 AM
To: development@qt-project.org
Subject: Re: [Development] Request for new Playground Repo

On Wednesday, 2013-11-20, 19:36:00, Andrew Wooster wrote:
 Hi, I'd like to request the creation of a new playground repository.

 Name: BlackBerry Extras

 Description: A repository for creating BlackBerry specific APIs that are
 useful for implementing Qt functionality.

 Let me know if there are any questions.

Since I saw PPS being mentioned as one of the extra APIs, isn't that also
available on stock QNX?

I.e. would it make sense to follow the naming used for the QPA or is the plan
to mostly add BB specific APIs?

Cheers,
Kevin

--
Kevin Krammer | kevin.kram...@kdab.com | Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-21 Thread Tony Van Eerd
Let's realize that there are probably 2 separate categories of code worth 
talking about, and then also some overlap:

A - common code for internal implementation
ie a PpsObject class would be used to implement many standard Qt APIs 
on the BB/QNX platform

B - useful code _for enduser developers_ that is only on one (or maybe 2) 
platform(s)
ie maybe Android Intent classes (or BlackBerry Invoke) if a reasonable 
cross-platform common API can't be found
Code like this is useful to get developers to use Qt - you don't want 
someone to say I'd use Qt except it doesn't give me access to special X on 
platform Y

A+B - code that falls into both categories
PpsObject might fall into this category - it is useful for internal 
implementation, but also useful for QNX-specific parts of a mostly 
cross-platform app.

I'd like locations for both A and B.  I suspect different locations.  And the 
A+B stuff is probably A stuff wrapped by classes in B.


 -Original Message-
 From: development-bounces+tvaneerd=rim@qt-project.org
 [mailto:development-bounces+tvaneerd=rim@qt-project.org] On Behalf
 Of Fabian Bumberger
 Sent: Thursday, November 21, 2013 4:16 AM
 To: development@qt-project.org; oswald.buddenha...@digia.com
 Subject: Re: [Development] Request for new Playground Repo
 
 Hi,
 
  so unless this is going to be a huge beast, maybe qtbase would be
 actually a better target?
 I agree that it would be much better to have it in QtBase, if this is
 possible. Above all, because certain parts there use PPS (e.g. QPA and
 Locale).
 And it is not a huge beast (see
 https://qt.gitorious.org/qt/qtlocation/source/469cbf8f601270ac0b030202a
 e303939ba4c63ff:src/plugins/position/blackberry/bb)
 
 Fabian
 
 From: development-bounces+fbumberger=blackberry@qt-project.org
 [development-bounces+fbumberger=blackberry@qt-project.org] on
 behalf of Kevin Krammer [kevin.kram...@kdab.com]
 Sent: Thursday, November 21, 2013 10:03 AM
 To: development@qt-project.org
 Subject: Re: [Development] Request for new Playground Repo
 
 On Wednesday, 2013-11-20, 19:36:00, Andrew Wooster wrote:
  Hi, I'd like to request the creation of a new playground repository.
 
  Name: BlackBerry Extras
 
  Description: A repository for creating BlackBerry specific APIs that
 are
  useful for implementing Qt functionality.
 
  Let me know if there are any questions.
 
 Since I saw PPS being mentioned as one of the extra APIs, isn't that
 also
 available on stock QNX?
 
 I.e. would it make sense to follow the naming used for the QPA or is
 the plan
 to mostly add BB specific APIs?
 
 Cheers,
 Kevin
 
 --
 Kevin Krammer | kevin.kram...@kdab.com | Software Engineer
 Klarälvdalens Datakonsult AB, a KDAB Group company
 Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
 KDAB - Qt Experts - Platform-independent software solutions
 -
 This transmission (including any attachments) may contain confidential
 information, privileged material (including material protected by the
 solicitor-client or other applicable privileges), or constitute non-
 public information. Any use of this information by anyone other than
 the intended recipient is prohibited. If you have received this
 transmission in error, please immediately reply to the sender and
 delete this information from your system. Use, dissemination,
 distribution, or reproduction of this transmission by unintended
 recipients is not authorized and may be unlawful.
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-21 Thread Vladimir Minenko

On 21.11.13 10:03, Kevin Krammer kevin.kram...@kdab.com wrote:

On Wednesday, 2013-11-20, 19:36:00, Andrew Wooster wrote:
 Hi, I'd like to request the creation of a new playground repository.
 
 Name: BlackBerry Extras
 
 Description: A repository for creating BlackBerry specific APIs that are
 useful for implementing Qt functionality.
 
 Let me know if there are any questions.

Since I saw PPS being mentioned as one of the extra APIs, isn't that also
available on stock QNX?

Yes, it is. We can target to make a new API for PPS which would unify
advantages of all current implementations and approaches. Still the fact
remains that a few things work on bare QNX in a different way than on BB10
because the latter is a complete application platform and the former is
just a pure OS.

I.e. would it make sense to follow the naming used for the QPA or is the
plan 
to mostly add BB specific APIs?

Does this mean considering QNX are a core platform and BB10 sitting on
top of it? This sounds sensible.

--
vm

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-21 Thread Peter Hartmann
On 11/20/2013 10:20 PM, Oswald Buddenhagen wrote:
 so unless this is going to be a huge beast, maybe qtbase would be
 actually a better target?

Even better if we could get the PPS parsing code directly into qtbase. 
As already posted, that comprises only a few files. Is everybody fine 
with that?

We might need a blackberry extras repo for other things later though...


Peter

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


[Development] Request for new Playground Repo

2013-11-20 Thread Andrew Wooster
Hi, I'd like to request the creation of a new playground repository.

Name: BlackBerry Extras

Description: A repository for creating BlackBerry specific APIs that are useful 
for implementing Qt functionality.

Let me know if there are any questions.

Thanks!

Andrew Wooster
Technical Lead
Development Platform
Office: (519) 597-9782
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread Oswald Buddenhagen
On Wed, Nov 20, 2013 at 07:36:00PM +, Andrew Wooster wrote:
 Hi, I'd like to request the creation of a new playground repository.
 
 Name: BlackBerry Extras
 
 Description: A repository for creating BlackBerry specific APIs that are 
 useful for implementing Qt functionality.
 
can you please elaborate on that?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread Andrew Wooster
Yes, that is the intent.

Andrew Wooster
Technical Lead
Development Platform
Office: (519) 597-9782


From: Knoll Lars [lars.kn...@digia.com]
Sent: 20 November 2013 14:51
To: Andrew Wooster; development@qt-project.org
Subject: Re: [Development] Request for new Playground Repo

On 20/11/13 20:36, Andrew Wooster awoos...@blackberry.com wrote:

Hi, I'd like to request the creation of a new playground repository.

Name: BlackBerry Extras

Description: A repository for creating BlackBerry specific APIs that are
useful for implementing Qt functionality.

Let me know if there are any questions.

If the purpose is the same as the other QPlatformExtras modules, I¹m happy
to add it.

Cheers,
Lars

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread Oswald Buddenhagen
On Wed, Nov 20, 2013 at 07:53:56PM +, Andrew Wooster wrote:
 Currently there is at least one API that is specific to BlackBerry
 that provides a wrapper for PPS

 that would be used in plugins supplied for Qt Location, as well as in
 Qt Systems.
 
that's the part that worries me slightly. what dependency graph between
the modules do you have in mind? where are the plugins going to end up?

 Essentially I'm trying to get something similar to the qt*extras modules 
 already present in Qt.
 
 Here's the reference for the one API that we'd immediately target for this 
 repository: 
 http://developer.blackberry.com/native/reference/cascades/bb__ppsobject.html
 
 Thanks
 
 Andrew Wooster
 Technical Lead
 Development Platform
 Office: (519) 597-9782
 
 
 From: development-bounces+awooster=blackberry@qt-project.org 
 [development-bounces+awooster=blackberry@qt-project.org] on behalf of 
 Oswald Buddenhagen [oswald.buddenha...@digia.com]
 Sent: 20 November 2013 14:46
 To: development@qt-project.org
 Subject: Re: [Development] Request for new Playground Repo
 
 On Wed, Nov 20, 2013 at 07:36:00PM +, Andrew Wooster wrote:
  Hi, I'd like to request the creation of a new playground repository.
 
  Name: BlackBerry Extras
 
  Description: A repository for creating BlackBerry specific APIs that are 
  useful for implementing Qt functionality.
 
 can you please elaborate on that?
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
 -
 This transmission (including any attachments) may contain confidential 
 information, privileged material (including material protected by the 
 solicitor-client or other applicable privileges), or constitute non-public 
 information. Any use of this information by anyone other than the intended 
 recipient is prohibited. If you have received this transmission in error, 
 please immediately reply to the sender and delete this information from your 
 system. Use, dissemination, distribution, or reproduction of this 
 transmission by unintended recipients is not authorized and may be unlawful.
 
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread Andrew Wooster
The QtLocation BlackBerry plugin already uses it, for one (but copies it 
locally).  We're also doing some work in QtSystems that also would use it for 
the BlackBerry implementation (but in the short term, we'll copy locally again).

I'll try and figure out if there's any other BlackBerry specific code in Qt 
that already copies it, but that's all I'm aware of right now.

Andrew Wooster
Technical Lead
Development Platform
Office: (519) 597-9782


From: development-bounces+awooster=blackberry@qt-project.org 
[development-bounces+awooster=blackberry@qt-project.org] on behalf of 
Oswald Buddenhagen [oswald.buddenha...@digia.com]
Sent: 20 November 2013 15:05
To: development@qt-project.org
Subject: Re: [Development] Request for new Playground Repo

On Wed, Nov 20, 2013 at 07:53:56PM +, Andrew Wooster wrote:
 Currently there is at least one API that is specific to BlackBerry
 that provides a wrapper for PPS

 that would be used in plugins supplied for Qt Location, as well as in
 Qt Systems.

that's the part that worries me slightly. what dependency graph between
the modules do you have in mind? where are the plugins going to end up?

 Essentially I'm trying to get something similar to the qt*extras modules 
 already present in Qt.

 Here's the reference for the one API that we'd immediately target for this 
 repository: 
 http://developer.blackberry.com/native/reference/cascades/bb__ppsobject.html

 Thanks

 Andrew Wooster
 Technical Lead
 Development Platform
 Office: (519) 597-9782

 
 From: development-bounces+awooster=blackberry@qt-project.org 
 [development-bounces+awooster=blackberry@qt-project.org] on behalf of 
 Oswald Buddenhagen [oswald.buddenha...@digia.com]
 Sent: 20 November 2013 14:46
 To: development@qt-project.org
 Subject: Re: [Development] Request for new Playground Repo

 On Wed, Nov 20, 2013 at 07:36:00PM +, Andrew Wooster wrote:
  Hi, I'd like to request the creation of a new playground repository.
 
  Name: BlackBerry Extras
 
  Description: A repository for creating BlackBerry specific APIs that are 
  useful for implementing Qt functionality.
 
 can you please elaborate on that?
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
 -
 This transmission (including any attachments) may contain confidential 
 information, privileged material (including material protected by the 
 solicitor-client or other applicable privileges), or constitute non-public 
 information. Any use of this information by anyone other than the intended 
 recipient is prohibited. If you have received this transmission in error, 
 please immediately reply to the sender and delete this information from your 
 system. Use, dissemination, distribution, or reproduction of this 
 transmission by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread Knoll Lars
On 20/11/13 21:05, Oswald Buddenhagen oswald.buddenha...@digia.com
wrote:

On Wed, Nov 20, 2013 at 07:53:56PM +, Andrew Wooster wrote:
 Currently there is at least one API that is specific to BlackBerry
 that provides a wrapper for PPS

 that would be used in plugins supplied for Qt Location, as well as in
 Qt Systems.
 
that's the part that worries me slightly. what dependency graph between
the modules do you have in mind? where are the plugins going to end up?

To some extent that¹s probably unavoidable if one of the main the IPC
mechanisms is platform specific. On Linux we also have a dbus dependency
on some of these backends.

Cheers,
Lars


 Essentially I'm trying to get something similar to the qt*extras
modules already present in Qt.
 
 Here's the reference for the one API that we'd immediately target for
this repository: 
http://developer.blackberry.com/native/reference/cascades/bb__ppsobject.h
tml
 
 Thanks
 
 Andrew Wooster
 Technical Lead
 Development Platform
 Office: (519) 597-9782
 
 
 From: development-bounces+awooster=blackberry@qt-project.org
[development-bounces+awooster=blackberry@qt-project.org] on behalf
of Oswald Buddenhagen [oswald.buddenha...@digia.com]
 Sent: 20 November 2013 14:46
 To: development@qt-project.org
 Subject: Re: [Development] Request for new Playground Repo
 
 On Wed, Nov 20, 2013 at 07:36:00PM +, Andrew Wooster wrote:
  Hi, I'd like to request the creation of a new playground repository.
 
  Name: BlackBerry Extras
 
  Description: A repository for creating BlackBerry specific APIs that
are useful for implementing Qt functionality.
 
 can you please elaborate on that?
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
 -
 This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other than
the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.
 
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Request for new Playground Repo

2013-11-20 Thread André Pönitz
On Wed, Nov 20, 2013 at 07:51:34PM +, Knoll Lars wrote:
 On 20/11/13 20:36, Andrew Wooster awoos...@blackberry.com wrote:
 
 Hi, I'd like to request the creation of a new playground repository.
 
 Name: BlackBerry Extras
 
 Description: A repository for creating BlackBerry specific APIs that are
 useful for implementing Qt functionality.
 
 Let me know if there are any questions.
 
 If the purpose is the same as the other QPlatformExtras modules, I¹m happy
 to add it.

I am not.

The general approach is wrong, for several reasons:

1. Splitting the platform extras already on the module level means that
everybody who wants to use some of the extras even buried behind #ifdef's
somewhere deep in his code has to add platform specific conditional code like

   !isEmpty(QT.x11extras.name) {
QT += x11extras
DEFINES += I_CAN_USE_X11EXTRAS
} else {
warning(x11extras module not found, )
}

to his buildsystem(s), for each of the platforms he want to fully
support. This is a maintanance burden not just for the buildsystem itself
but also extends to conditional packaging/installation.

2. The setup is inherently fragile as only part of the code is used, and part
not even checked on a specific developer's machine at a time, bearing the
risk of the classic compile fix or CI ping pong.

3. The approach does not scale as it does not offer a natural place for
features that are not available on all platforms, but on more then one.
Putting random sort-of-sharable code into qtbase is not a good alternative
either.


There is no perfect solution, but the further down the conditionals 
are in the code the less impact they have on all three aspects, and
the more code can be shared between the backends.

Merging the platform into a single module with fat #ifdefs QT_OS_XYZ
in the headers would already alleviate the problem on the build system
level, and upwards (packaging...), while providing the same interface
to the actual code. That'd be a uniform improvemnt over the current setup.

Andre'
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development