[Development] Question on QWS/QPA

Arunprasad Rajkumar ararunprasad at gmail.com
Tue Dec 11 10:24:09 CET 2012


Thanks Samuel. If possible point me some QWS guys :)

On 11 December 2012 14:38, Samuel Rødal <samuel.rodal at digia.com> wrote:

> On 12/11/2012 09:53 AM, Arunprasad Rajkumar wrote:
>
>> Hi Samuel,
>>
>> Thanks for your reply. We would like to have only QtWebKit widget and
>> not going to use QtQuick at this moment. So by default QPA/QWS client
>> will render widgets on shared memory allocated via Qt and draws on it.
>> Once done it request the QPA/QWS server to do the composition of
>> widgets. Am I right?
>>
>> As I mentioned, I would like to proxy the rendering calls(not all, only
>> few like blit/fill) to server. Is there anyway to differentiate Server &
>> Client process in gfxplugin? Some Qt QWS documents
>> <http://doc.qt.digia.com/qt/**qt-embedded-accel.html<http://doc.qt.digia.com/qt/qt-embedded-accel.html>>says
>> like,
>>
>> "The connect() <http://doc.qt.digia.com/qt/**qscreen.html#connect<http://doc.qt.digia.com/qt/qscreen.html#connect>>
>> and
>> disconnect() <http://doc.qt.digia.com/qt/**qscreen.html#disconnect<http://doc.qt.digia.com/qt/qscreen.html#disconnect>>
>> are
>>
>> called by both the server and client processes, while the initDevice()
>> <http://doc.qt.digia.com/qt/**qscreen.html#initDevice<http://doc.qt.digia.com/qt/qscreen.html#initDevice>>
>> and
>> shutdownDevice()
>> <http://doc.qt.digia.com/qt/**qscreen.html#shutdownDevice<http://doc.qt.digia.com/qt/qscreen.html#shutdownDevice>>
>> functions are
>>
>> only called by the server process."
>>
>> Once I differentiate it, then I can proxy the rendering calls.
>>
>
> Unfortunately I'm only familiar with QPA and not with QWS. In QPA (at
> least in Qt 5) there's QBlittablePlatformPixmap and QBlittable which might
> let you do something like that.
>
> --
> Samuel
>
>


-- 
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121211/7081c5ab/attachment.html>


More information about the Development mailing list