Thanks Samuel. If possible point me some QWS guys :)
On 11 December 2012 14:38, Samuel Rødal 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 d
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 r
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
On 12/06/2012 08:00 PM, Arunprasad Rajkumar wrote:
> Hello Developers,
>
> I'm new to QT. Basically I understood like QWS/QPA reduces porting QT to
> custom embedded devices without touching the core functionality of
> QtGui. Also it is a architectural split down of functionality and
> porting laye
Hello Developers,
I'm new to QT. Basically I understood like QWS/QPA reduces porting QT to
custom embedded devices without touching the core functionality of QtGui.
Also it is a architectural split down of functionality and porting layer.
QWS is a legacy model & have some limitation, so we can't f
