|
As GL call would have
to be emulated by SW, the use of multiple screen has some
limitations. Nevertheless, the technology could be very
interesting for :
- remote debug - remote simple applications. The second case is what I feel would provide the most value. If I take the example of an IVI or a TV, there is a strong demand to provide connectivity with external gadget such as tablet of phone, for basic application such as remote control. The traditional model requires to develop an App per gadget (and often per gadget release) and to maintain them in sync with the SW on the IVI or TV main device. The multiple target induces already a hard work but the second, the sync SW requirement can quickly become a nightmare when the main device SW update/upgrade model is control regionally (by Car dealers for IVI and by requirement to comply to broadcast API such as HBB for TV) while the App of the connected gadget will be updated by an App market on a worlwide basis. The RDP model can help to ease that requirement a lot, by requiring only one RDP client per gadget which only need to be in sync with the gadget SW (the RDP protocol stability is assumed). QA only need to validate once the RDP client per gadget. Then as the App which "seems" to be running on the gadget is actually running in the main device, there is no risk to get out of Sync. QA work would obviously simplify as the beside of checking various display ratio, there is nothing requiring further qualification for each App related to gadget. In short, I can see many applications which could benefit of this model. My 2 pence initial list would be : * TV - TV remote control - Media centre remote with covert ART * IVI - Radio remote control - Free parking space lock up by passenger and push new destination to GPS. Thoughts ? Dominig ar Foll Senior Architect Intel Open Source Technology CentreLe 07/04/2014 10:35, Manuel Bachmann a écrit :
|
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
