I think code that isn't specific to the automotive industry such as as the dbus 
integration should be integrated into existing modules unless there is a good 
reason otherwise.

Just my two cents,
Simon

From: Viironen Kalle
Sent: Tuesday, October 13, 2015 09:35
To: development@qt-project.org
Subject: [Development] New Qt Modules


Hi,

We'd like to have a bunch of new modules under qt-project. These are all needed 
in Qt Automotive Suite so let's try to get this sorted out quickly to get 
things rolling nicely.

New repositories needed are:

  *
qt/qtapplicationmanager, Qt component for application lifecycle management
  *   qt/qtdbusqml, Qt QML DBus integration
  *   qt/qtivi, Qt IVI extensible platform abstraction layer
  *   qt/qtgeniviextras, Qt extras for GENIVI services
  *   qt-apps/qmllive, QmlLive live reloader environment for rapid UI 
development
  *   qt-apps/neptune-ui, The Neptune Automotive Reference UI
  *   qt-apps/neptune-appstore, The Neptune Reference Application Store Server

Best Regards,

Kalle Viironen

Senior Manager, Device Creation | The Qt Company


The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland

Email: kalle.viiro...@theqtcompany.com<mailto:kalle.viiro...@theqtcompany.com> 
| Mobile: + 358 40 50 10989

www.qt.io | Qt Blog: http://blog.qt.digia.com/ | Twitter: @QtbyDigia, 
@Qtproject | Facebook: www.facebook.com/qt

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to