[Qt5-feedback] integrated remote control server system

[BRM]

While I am not Qt/Nokia/etc - I'm not sure a Remote Control thing would be 
really part of Qt; that sounds a lot like how you design your specific 
application/services than something that is part of the platform.
That said, it could certainly be made easier by things like D-Bus (supported via 
QtDbus); though making it obvious how to do a network-oriented D-Bus would be 
extremely helpful.[1]

And FYI - I am doing something similar with Remote Applications; though I do not 
hack into Qt to do it - it's a matter of the protocols (application specific - 
some XML, some binary) and design of the application (network-based, distributed 
architecture).

Ben

[1] I have a series of applications that I essentially implemented my own 
version of D-Bus for b/c at the time while I liked D-Bus, I couldn't figure out 
how to make it work with a network architecture which was an absolute must for 
my own applications. Since then I have learned it can be done, but it is still 
not very obvious at least to me. Doing it again, I'd probably try to stick to 
D-Bus.


>
>From: Thomas Ganshorn <mailings at novaimages.de>
>To: "qt5-feedback at qt.nokia.com" <qt5-feedback at qt.nokia.com>
>Sent: Thu, May 12, 2011 12:36:38 PM
>Subject: [Qt5-feedback] integrated remote control server system
>
>  
>Just a request and/or idea.
> 
>i have many applications i need to remote control.
>Easiest for now is using an html interface because every machine has an html 
>browser.
>Something qt quick cannot solve.
> 
>So what i did was a simple hacked http server inside of qt exposing selected 
>objects and properties allowing custom websites to control the application or 
>presenting informations.
> 
>Regardless of the protocol (although http is really a must have)
>i think in the modern connected world it is not uncommon to have a server 
>application and a remote gui.
> 
>So what i really would like would be a REAL platform independent and working
>-> integrated mechanism to generate proxy QObjects over the network (on all 
>plattforms)
>   for eg having a qml ui in another process on another machine.
>   Probably a real client qml viewer would be also possible ... loading the qml 
>informations from the masterprocess
>   creating locally the objetcs to talk to and have a remote talk with the 
>server app.
> 
>-> an integrated http server that allows at least exposing interfaces and custom 
>handling.
>   An external http server is in many cases not even an option.
>   May it because of installation, the additional ipc overhead, or probably just 
>forbidden by the client.
   (As stated i wrote already a hacked solution for this but ... it is only a 
hack). 

> 
> 
>So an integrated option to remote control applications with not too much 
>overhead in development and speed.
>For our FlowLine system (just as an example) the 3d artists really loved the 
>ability to define parameters
>that can be controlled externally on their ipad or see the state of the 
>fluidsimulaton on the farm.
>It got a real time and moneysaver.
> 
>For other stuff like home automation it also makes perfect sense.
> 
> 
> 
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt.nokia.com/pipermail/qt5-feedback/attachments/20110512/0d225265/attachment.html