in_dbasu
20th May 2011, 10:57
Pros:
1.Embed third party applications in the container widget allowing integration of QT with third party application.
2.Follows XEmbed protocol which allows embedding the XEmbed widgets to be embedded to the container.
3.Can embed Xembed widget, but the windows ID of the widget needs to be passed on to the container.
Cons:
1. In case of third party applications the windows ID of the application needs to be passed on to the container to embed the application to the container.
2.There is no way container or QT can know the windows ID of the application thereby the application cannot be embedded to the container programmatically.
3.The windows ID of third party applications can be obtained manually by the xwininfo command from the command prompt. But for practiacal purpose this method is of no use for any integrated application containing QT container and third party application.
4. If the above points are true then practically there is of no use for QX11EmbeddedContainer in QT.
1.Embed third party applications in the container widget allowing integration of QT with third party application.
2.Follows XEmbed protocol which allows embedding the XEmbed widgets to be embedded to the container.
3.Can embed Xembed widget, but the windows ID of the widget needs to be passed on to the container.
Cons:
1. In case of third party applications the windows ID of the application needs to be passed on to the container to embed the application to the container.
2.There is no way container or QT can know the windows ID of the application thereby the application cannot be embedded to the container programmatically.
3.The windows ID of third party applications can be obtained manually by the xwininfo command from the command prompt. But for practiacal purpose this method is of no use for any integrated application containing QT container and third party application.
4. If the above points are true then practically there is of no use for QX11EmbeddedContainer in QT.