On 08/03/2011 06:01 PM, Jeremiah Foster wrote:
Any comments?
I would go with this type of API segments divided according to the
level and ease of access:
for all developers:
- QtQuick signals and data models.
So developers would only have access to "data models" and Qt Signals?
Not the actual data structures themselves? This would seem to preclude
talking to things like Diagnostic Log and Trace. Or the compositor. Or
systemd, should that be used.
yes, and I don't think that is a problem for a software in the category
of 'apps'
for tier 1 developers
- Qt API
This excludes ECU to ECU communication. Tier 1's would likely never
accept this.
Nor will any legislator approve MeeGo based systems to be used in any
sort of safety critical or even safety aware systems. Crafting an API
for automotive control systems is not the issue here, as the software
stack won't get certificated for use in safety critical systems.
There are some questions about the viability of dbus in the automotive
environment due to the fact that it is considered slow in comparison
to other embedded IPC systems.
such as?
This would also nicely handle the security issue as the dbus is
already a system bus with established session control and safety
features. Customisation is also possible from QML all the way down
to the dbus for those who absolutely need it through the Qt dbus
interface. SocketCAN which was discussed earlier could be revealed
as a dbus object as could be done with any other additional
vehicle bus.
This would likely be extremely limiting and would hardly be sufficient
for the automotive environment. A car is not a phone.
sure thing but IVI is about infotainment systems not control systems. I
think you are slightly out of focus here. Most dashboard information
devices are actually quite close to smart phones. Navigation, speech
controls, telephony, BT hands-free, media player, radio ... Those are
all functionalities found in both targets, the cars and the smart phones.
BR
- jive
_______________________________________________
MeeGo-ivi mailing list
[email protected]
http://lists.meego.com/listinfo/meego-ivi
