On Sunday, 7 de August de 2011 08:21:40 Holger Freyther wrote:
> 1.) Extending the QPlatformIntegration in the future:
> 
> What is the plan for adding new virtual functions to the
> QPlatformIntegration interface?
> 
> - Providing a new QPlatformIntegrationPlugin?
> - Providing a version inside QPlatformIntegration and subclass it
>   and then ask for a specific version to be created?
> 

They are being added in Qt 5 right now. I don't know what the best solution 
for Qt 5.1, though. What we've done in Qt in the past is subclass and create a 
V2 class, so we know which new virtuals have been implemented.

> 2.) Finding out on which platform one runs.
> 
> - in WebKit we use defined(Q_WS_...) to detect the platform or sometimes
>   use the QX11Info class or other things.
> 
> How is this supposed to work with QPA/Lighthouse? How would I get the
> native display connection (e.g. if I want to/need to by pass Qt)? Are
> there some best practices?

First option: don't do it. Write agnostic code that doesn't depend on the 
platform. If you need to access the display connection for something, it might 
indicate a missing API in Qt or the platform plugin.

So really let's try and fix Qt and your code first before you need to try and 
access the  native. This is especially important in the first Qt 5.x releases, 
as we'll need to identify what's missing.

That said, there will be legitimate uses of native API. We'll probably need 
run-time functions to tell you which one it is. The Q_OS_xxx macros will still 
be there, so you'll know whether you can link to Cocoa frameworks or to Win32 
libs.

Now here's a good question: how do I write a Lighthouse program that embeds 
another program? Do I use QX11EmbedContainer or QMacCocoaViewContainer? The 
long-term answer will probably be a QML item, but until QML is ready for the 
desktop, how do I my app?

Another would be a question of whether to link to X11 or libwayland or 
something else on Q_OS_LINUX. The answer will probably be to make them plugin.

> 3.) QPixmap laoding/image decoder
> 
> There is HW that can decode certain image formats in hardware and store it
> in video memory directly. Is there any plan to add support for that? Would
> there be any objection to such features?

I thought that there was already some code doing it. Especially for the JPEG 
decoding.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback

Reply via email to