From dominik.holland at pelagicore.com Thu Jun 2 13:38:06 2016 From: dominik.holland at pelagicore.com (Dominik Holland) Date: Thu, 2 Jun 2016 13:38:06 +0200 Subject: [Automotive] QtIviMedia vs QtMultimedia In-Reply-To: <85725531-346D-44A5-B761-B04A273C4713@qt.io> References: <85725531-346D-44A5-B761-B04A273C4713@qt.io> Message-ID: <5d64aba8-4224-313a-55a0-3ea385ad4720@pelagicore.com> Hi, as the indexing,searching and browsing would be the most part of the api, i think the overlap is quite thin. It's really only the basic toplayer player api which is needed, nothing from the underlying qtmultimedia backends or the audio-managment/camera etc. is used. I already started with the design of it and have a prototype of it. I still think the module makes sense to have and as it's part of qtivi it has a completely different architecture and also a different scope. qtivi is meant for system-ui development in the automotive space and just provides you a core of apis which can be extended by the OEM. Most of the OEMs don't do the backend development by their own. Instead they just define an IPC and define that this needs to be used. This means it's not possible reuse one backend of a OEM by another OEM. The feature sets are also totally different and the goal here is not to provide a full-featured API with a working backend. We just provide a skeleton for the core aspect of the usecases and a simulation backend. Everything else needs to be done by the OEM himself. For media this means, there will be a basic player api for play/stop/next/previous the media and it's basically translating these calls almost one to one to a backend-interface which makes the API very thin, but easy to extend by the OEM. Usually the qtivi backend is then calling a OEM specific IPC calls to a OEM specific implementation of the actual mediaplayer. This mediaplayer is then implementing all the needed interfaces e.g. browsing, searching, sharing, indexing, usb-device discovery, apple device discovery, DLNA etc.). I don't think it would make much sense if the backend for the media-player would be half implemented in qtmultimedia (for the mediaplayer part) and the rest (browsing, search, indexing...) is implemented as a backend in a separate repository with no direct way for the two plugins to interact with each other. The same goes other APIs needed in the automotive space, which may fit a little bit with qtmultimedia, but it's hard to make it easy for the OEM to write the backend and extend them. E.g. camera. QtMultimedia has a camera api so we should try to reuse it, but this camera api is intended for app developers to control the camera settings like exposure... and maybe take photos or videos. The rear-view camera of a car needs a totally different api, because the exposure and settings like this are not exposed to the UI at all, this is done by some backend which talks directly to the camera. The camera is usually controlled in connection with some other sensors and comes as a hardware-composited overlay. How surfaces like this are integrated in QML (and whether they are) is also different by every OEM. As QtMultimedia is supposed to work on all the tier-1 platforms i guess the API should work on the tier-1 platforms as well, which means we would need a backend which supports the playqueue management and all the other features we need to support in automotive there as well. Otherwise we would introduce APIs in QtMultimedia which you can't test on any platform as there is no backend implementing them. I also think that when introducing a full set of new features into the existing API we might break a lot of things. I would see the qtivimedia module similar to other existing apis like qtgstreamer or phonon in the old days, which tries to solve a different problem and may overlap a little bit with other APIs. So i would propose to see the QtIviMedia apis as a test-balloon and see whether the dynamic backend changing, the browsing and api works as such and then think about moving features back to QtMultimedia and replace our apis with them. This can be done as QtIvi will have it's own version similar to the QtVirtualKeyboard and we can increase the version number if we see a need to break the compatibility. Dominik Am 05/31/2016 um 01:46 PM schrieb Yoann Lopes: > Hi, > > I think it would make more sense to add the missing APIs to QtMultimedia > rather than create a new module. That module would be redundant for the > most part. > > The only part that could make sense to be in a separate module are the > media searching/browsing/indexing. Actually, I?d make that more generic > to handle different kind of files and put it in QtCore. > >> The reason for this is that it is common in IVI systems to have >> out-of-process media rendering engines and we don't want to integrate >> them as QtMultimedia backends as they really do not fit. > In what way don?t they fit? The backend API could be extended to handle > this case if there?s just no way to do it currently. > > ? > Yoann > > >> On 24 May 2016, at 14:41, Johan Thelin > > wrote: >> >> Hi, >> >> I would say that QtMultimedia is for in-process media rendering, while >> QtIVIMedia is about media indexing/browsing and out-of-process >> rendering. Of course QtMultimedia can be used to implement a rendering >> backend support in-process rendering, but that is not at the top of >> the list right now. >> >> The reason for this is that it is common in IVI systems to have >> out-of-process media rendering engines and we don't want to integrate >> them as QtMultimedia backends as they really do not fit. >> >> Best regards, >> >> --- >> >> Johan Thelin ??? ??? >> M.Sc.E.E. >> System Architect >> >> PELAGICORE | Experience Change >> Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden >> Mobile: +46 (0)700 900 250 >> Skype: jothpelagicore >> E-Mail: johan.thelin at pelagicore.com >> >> On 24 May 2016 at 08:51, Marko Kangas > > wrote: >> >> >> I think this should be discussed also with QtMultimedia maintainer >> Yoann Lopes (cc). >> >> I'm not decision maker but in general I think we should use API >> and module we already have. Just extend it to fill automotive >> purposes. But I don't know details if it's not doable and there's >> some specific issues then it might be relevant to think separate >> API. It just might be confusing why to have several similar sound >> APIs. >> >> Yoann, could you check mail below from Dominik. Maybe you have >> some opinion from the QtMultimedia side? >> >> Br, Marko >> >> >> >> -----Original Message----- >> From: Automotive [mailto:automotive-bounces+marko.kangas >> =qt.io at qt-project.org >> ] On Behalf Of Dominik Holland >> Sent: 23. toukokuuta 2016 15:34 >> To: automotive at qt-project.org >> Subject: [Automotive] QtIviMedia vs QtMultimedia >> >> Hi, >> >> according to our roadmap, one of the next things are the >> development of >> RadioTuner APIs and to support all automotive multimedia usecases. >> >> The first thought for this would be the QMediaPlayer and the QRadio >> classes which are part of QtMultimedia. >> >> The last week i did a gap analysis and checked the classes and the >> backend interfaces for whether they support all the automotive >> features. >> >> The outcome is the following: >> >> QRadio: >> * No support for background scanning >> * No interfaces for DAB, SDARS (satelite), HDRadio >> * No interfaces for a DB to save favorite stations (presets) or >> already >> scanned stations >> * No metaData support (RadioText +, DAB media content) >> * No announcment system >> * No way to browse Channel categories >> * No way to search for stations >> >> QMediaPlayer/QMediaPlaylist: >> * No way to change mediabackend from QML (e.g. switch to control the >> playback on my mobile phone) >> * No way to get all available media backends >> * MediaPlaylist only stores the urls, but not the metadata, this is >> retrieved only for the current file playing >> * No API for managing multi playlists >> * No media browsing api >> * No media search API >> * No Indexing control API >> >> I think the QtMultimedia APIs are really meant to be >> cross-platform and >> should give the developer an easy way to playback their media content >> and integrate it into their own Application. >> >> The QtIviMedia APIs on the other hand are more meant for system >> developers to use an underlying system MediaPlayer and also have >> in mind >> to control other devices like a connected mobile phone (bluetooth) >> or a >> RSE system. >> >> Because QtMultimedia doesn't offer all the features we need and we >> need >> the new APIs soon, i would propose to do the QtIviMedia development >> without using QtMultimedia classes in the developer facing APIs. >> For the >> simulation APIs i think it's very valid to use the QtMultimedia >> APIs to >> make the simulation work on every development system. >> >> Do you all agree with that ? >> >> Best Regards >> Dominik >> >> _______________________________________________ >> Automotive mailing list >> Automotive at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/automotive >> _______________________________________________ >> Automotive mailing list >> Automotive at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/automotive >> >> > -- Dominik Holland SENIOR SOFTWARE ENGINEER Pelagicore AG Balanstr. 55, 81541 Munich, Germany +49 (0)171 760 25 96 dominik.holland at pelagicore.com www.pelagicore.com From 754833745 at qq.com Sat Jun 11 08:54:57 2016 From: 754833745 at qq.com (=?ISO-8859-1?B?TGFycnk=?=) Date: Sat, 11 Jun 2016 14:54:57 +0800 Subject: [Automotive] Hello everyone Message-ID: Hello, everyone. I am a new gay in IVI system. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vladstelmahovsky at gmail.com Sat Jun 11 19:12:36 2016 From: vladstelmahovsky at gmail.com (Vlad Stelmahovsky) Date: Sat, 11 Jun 2016 19:12:36 +0200 Subject: [Automotive] Hello everyone In-Reply-To: References: Message-ID: No one cares about your preferences :) On Sat, Jun 11, 2016 at 8:54 AM, Larry <754833745 at qq.com> wrote: > Hello, everyone. > I am a new gay in IVI system. > > _______________________________________________ > Automotive mailing list > Automotive at qt-project.org > http://lists.qt-project.org/mailman/listinfo/automotive > > -- Best regards, Vlad -------------- next part -------------- An HTML attachment was scrubbed... URL: From louai.al-khanji at qt.io Tue Jun 14 20:06:58 2016 From: louai.al-khanji at qt.io (Louai Al-Khanji) Date: Tue, 14 Jun 2016 18:06:58 +0000 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: <747926A2-B3EF-4F20-BBDE-84C61D077B3C@qt.io> >> I would like to share the meta-qt5-ivi which provides qtapplicationmanager, >> qtivi and qt-apps-neptune-ui. >I am not thinking so much about a feature by feature comparison but the practicalities about >layer architecture and adoption. To give one example the Genivi Development Platform (GDP) >uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work >into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5 >raises questions of maintenance going forward and whether all requirements are met, whilst just adopting >the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. Hi all, In the interest of avoiding fragmentation, I would like to invite interested parties to work with us to make sure that there is one place that provides high-quality recipes for these components. These components are included in our newly-public meta-boot2qt layer: http://code.qt.io/cgit/yocto/meta-boot2qt.git/ The README provides a good overview: http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/README meta-boot2qt builds on meta-qt5 to provide amongst other things more up to date versions of Qt [1] and the above automotive packages [2]. It includes a poky-based reference distro, but the recipes can certainly be used independently. meta-boot2qt also provides support for a lot of devices. Currently this includes the i.MX6, i.MX7, Rcar Gen 2, Raspberry Pi 1/2/3, Jetson Pro/Tegra, VirtualBox, Intel. The full list can be seen in our layer init script [3]. The layer is developed in the open through Qt Code Review (i.e. gerrit) [4]. I am very happy to see the wide-spread interest in these components. We welcome people to work with us to establish one high-quality, canonical upstream for the recipes. Cheers, Louai [1] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/qt5 [2] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/automotive [3] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/b2qt-init-build-env [4] https://codereview.qt-project.org From louai.al-khanji at qt.io Tue Jun 14 20:15:37 2016 From: louai.al-khanji at qt.io (Louai Al-Khanji) Date: Tue, 14 Jun 2016 18:15:37 +0000 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: <49397B5F-B6D3-4C6C-909A-D88B028C3AAA@qt.io> >> I would like to share the meta-qt5-ivi which provides qtapplicationmanager, >> qtivi and qt-apps-neptune-ui. >I am not thinking so much about a feature by feature comparison but the practicalities about >layer architecture and adoption. To give one example the Genivi Development Platform (GDP) >uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work >into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5 >raises questions of maintenance going forward and whether all requirements are met, whilst just adopting >the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. > Hi all, In the interest of avoiding fragmentation, I would like to invite interested parties to work with us to make sure that there is one place that provides high-quality recipes for these components. These components are included in our newly-public meta-boot2qt layer: http://code.qt.io/cgit/yocto/meta-boot2qt.git/ The README provides a good overview: http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/README meta-boot2qt builds on meta-qt5 to provide amongst other things more up to date versions of Qt [1] and the above automotive packages [2]. It includes a poky-based reference distro, but the recipes can certainly be used independently. meta-boot2qt also provides support for a lot of devices. Currently this includes the i.MX6, i.MX7, Rcar Gen 2, Raspberry Pi 1/2/3, Jetson Pro/Tegra, VirtualBox, Intel. The full list can be seen in our layer init script [3]. The layer is developed in the open through Qt Code Review (i.e. gerrit) [4]. I am very happy to see the wide-spread interest in these components. We welcome people to work with us to establish one high-quality, canonical upstream for the recipes. Cheers, Louai [1] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/qt5 [2] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/automotive [3] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/b2qt-init-build-env [4] https://codereview.qt-project.org From louai.al-khanji at qt.io Tue Jun 14 21:25:59 2016 From: louai.al-khanji at qt.io (Louai Al-Khanji) Date: Tue, 14 Jun 2016 19:25:59 +0000 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> <49397B5F-B6D3-4C6C-909A-D88B028C3AAA@qt.io> Message-ID: Hello Rudi, In the interest of avoiding fragmentation, I would like to invite interested parties to work with us to make sure that there is one place that provides high-quality recipes for these components. These components are included in our newly-public meta-boot2qt layer: http://code.qt.io/cgit/yocto/meta-boot2qt.git/ The README provides a good overview: http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/README Is this based on "Qt for Device Creation" (http://www.qt.io/qt-for-device-creation/)? At least the README mentions it. A while ago I wanted to give Qt for Device Creation a try for a hobby project but it seems to be commercially licensed only and there was only a 30 day free trial available. That still seems to be the case according to the website. Could you please clarify the licensing? It looks as if the layer itself is GPLv3-licensed. What about the boot2qt components? You are exactly right, this is the layer that we use to build the references images for Qt for Device Creation. Per se, there are very few Boot2Qt-specific components. Boot2Qt simply is a reference distro based on Poky that pulls in various bits and pieces, including more of Qt than is packaged in meta-qt5. It?s not meant to duplicate existing work, we do try to push as much as possible upstream. In fact, meta-boot2qt depends on meta-qt5. As for Qt itself, the latest licensing is described e.g. here: http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/ Most of the base components have always been open - the bulk of the code, after all, is in the Qt framework itself. Recently a lot of the components that are more embedded-specific have also been opened up. I would need to check which remain commercial-only, but there aren?t very many. I?d actually be interested to hear whether you have any specific ones in mind. There are a few parts of the host tooling that are not open right now - for instance we do have a plugin that talks to ADB directly so that you can just plug your device into a USB port instead of having to mess with networking to get remote deployment/debugging/profiling. These however add convenience rather than being 100% necessary per se. meta-boot2qt builds on meta-qt5 to provide amongst other things more up to date versions of Qt [1] and the above automotive packages [2]. It includes a poky-based reference distro, but the recipes can certainly be used independently. meta-boot2qt also provides support for a lot of devices. Currently this includes the i.MX6, i.MX7, Rcar Gen 2, Raspberry Pi 1/2/3, Jetson Pro/Tegra, VirtualBox, Intel. The full list can be seen in our layer init script [3]. The layer is developed in the open through Qt Code Review (i.e. gerrit) [4]. I am very happy to see the wide-spread interest in these components. We welcome people to work with us to establish one high-quality, canonical upstream for the recipes. Looks like it is a fully distro layer. I will give it a shot. It is. Looking forward to your feedback! One thing that is good to know is that currently some recipes pull from codereview.qt.io directly. That?s the easiest setup for us, but it does require you to have a gerrit account. It?s on my TODO list to fix that where possible. Cheers, Louai -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.bollo at iot.bzh Tue Jun 14 17:05:50 2016 From: jose.bollo at iot.bzh (=?UTF-8?Q?Jos=C3=A9_Bollo?=) Date: Tue, 14 Jun 2016 17:05:50 +0200 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: <5760083D.7040702@gmail.com> References: <5760083D.7040702@gmail.com> Message-ID: Hi Phong, That is interesting. I see the file https://github.com/phongt/meta-qt5-ivi/blob/dev/recipes-qt/qt5/qtwebengine_git.bbappend Is it what is needed to compile qtwebengine with gcc5 If yes, I think that it should be submitted in AGL upstream Best regards Jos? Bollo Jos? Bollo - Senior Software Engineer www.iot.bzh 2016-06-14 15:35 GMT+02:00 phongtran : > Hi ALL, > > I would like to share the meta-qt5-ivi which provides > qtapplicationmanager, qtivi and qt-apps-neptune-ui. > > The repo is on github here: > https://github.com/phongt/meta-qt5-ivi > > I applied this layer to AGL distro and It can start up QEMU x86-64 KVM > Ubuntu 14.04 host PC. > > Please refer README for detail: > https://github.com/phongt/meta-qt5-ivi/blob/dev/README > > I uploaded the images here: > > > https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc&usp=sharing > > I attached some screenshoots of Neptune UI. > > Please review and give your feedbacks. > Thank you. > > Regards, > Phong. > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From changhyeok.bae at gmail.com Tue Jun 14 17:14:13 2016 From: changhyeok.bae at gmail.com (Changhyeok Bae) Date: Wed, 15 Jun 2016 00:14:13 +0900 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: Neptune UI is really interesting. :) 2016-06-15 0:05 GMT+09:00 Jos? Bollo : > Hi Phong, > > That is interesting. > > I see the file > https://github.com/phongt/meta-qt5-ivi/blob/dev/recipes-qt/qt5/qtwebengine_git.bbappend > Is it what is needed to compile qtwebengine with gcc5 > > If yes, I think that it should be submitted in AGL upstream > > Best regards > Jos? Bollo > > Jos? Bollo - Senior Software Engineer > www.iot.bzh > > > 2016-06-14 15:35 GMT+02:00 phongtran : > >> Hi ALL, >> >> I would like to share the meta-qt5-ivi which provides >> qtapplicationmanager, qtivi and qt-apps-neptune-ui. >> >> The repo is on github here: >> https://github.com/phongt/meta-qt5-ivi >> >> I applied this layer to AGL distro and It can start up QEMU x86-64 KVM >> Ubuntu 14.04 host PC. >> >> Please refer README for detail: >> https://github.com/phongt/meta-qt5-ivi/blob/dev/README >> >> I uploaded the images here: >> >> >> https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc&usp=sharing >> >> I attached some screenshoots of Neptune UI. >> >> Please review and give your feedbacks. >> Thank you. >> >> Regards, >> Phong. >> >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions at lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> >> > > _______________________________________________ > genivi-projects mailing list > genivi-projects at lists.genivi.org > https://lists.genivi.org/mailman/listinfo/genivi-projects > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.lawrence at renesas.com Tue Jun 14 18:27:23 2016 From: stephen.lawrence at renesas.com (Stephen Lawrence) Date: Tue, 14 Jun 2016 16:27:23 +0000 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: <5760083D.7040702@gmail.com> References: <5760083D.7040702@gmail.com> Message-ID: Hi Phong, > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of phongtran > Sent: 14 June 2016 14:36 > To: automotive-discussions at lists.linuxfoundation.org > Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org > Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) > > Hi ALL, > > I would like to share the meta-qt5-ivi which provides qtapplicationmanager, > qtivi and qt-apps-neptune-ui. > > The repo is on github here: > https://github.com/phongt/meta-qt5-ivi > > I applied this layer to AGL distro and It can start up QEMU x86-64 KVM > Ubuntu 14.04 host PC. > > Please refer README for detail: > https://github.com/phongt/meta-qt5-ivi/blob/dev/README > > I uploaded the images here: > > https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc& > usp=sharing > > I attached some screenshoots of Neptune UI. > > Please review and give your feedbacks. Looks interesting. Thank you for sharing. One question from reading the Readme. I see it does not use the existing meta-qt5 layer [1]. Whilst trying to avoid drawing you into politics could you summarise technically why your layer has its own base Qt 5 parts? From a quick look the two layers seem to have a somewhat different focus and you've provided recipes presumably for just what you need. I am not thinking so much about a feature by feature comparison but the practicalities about layer architecture and adoption. To give one example the Genivi Development Platform (GDP) uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5 raises questions of maintenance going forward and whether all requirements are met, whilst just adopting the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. [1] https://github.com/meta-qt5/meta-qt5 Regards Steve From changhyeok.bae at gmail.com Tue Jun 14 19:20:23 2016 From: changhyeok.bae at gmail.com (Changhyeok Bae) Date: Wed, 15 Jun 2016 02:20:23 +0900 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: If you agree, +1 Stephen's opinion. 2016-06-15 1:27 GMT+09:00 Stephen Lawrence : > Hi Phong, > > > -----Original Message----- > > From: automotive-discussions-bounces at lists.linuxfoundation.org > > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > > Behalf Of phongtran > > Sent: 14 June 2016 14:36 > > To: automotive-discussions at lists.linuxfoundation.org > > Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org > > Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) > > > > Hi ALL, > > > > I would like to share the meta-qt5-ivi which provides > qtapplicationmanager, > > qtivi and qt-apps-neptune-ui. > > > > The repo is on github here: > > https://github.com/phongt/meta-qt5-ivi > > > > I applied this layer to AGL distro and It can start up QEMU x86-64 KVM > > Ubuntu 14.04 host PC. > > > > Please refer README for detail: > > https://github.com/phongt/meta-qt5-ivi/blob/dev/README > > > > I uploaded the images here: > > > > https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc& > > usp=sharing > > > > I attached some screenshoots of Neptune UI. > > > > Please review and give your feedbacks. > > Looks interesting. Thank you for sharing. > > One question from reading the Readme. I see it does not use the existing > meta-qt5 layer [1]. > Whilst trying to avoid drawing you into politics could you summarise > technically why your layer > has its own base Qt 5 parts? From a quick look the two layers seem to have > a somewhat different focus > and you've provided recipes presumably for just what you need. > > I am not thinking so much about a feature by feature comparison but the > practicalities about > layer architecture and adoption. To give one example the Genivi > Development Platform (GDP) > uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone > wanted to adopt your work > into GDP the question arises as to how best to do that. Adopting your Qt5 > layer instead for the base Qt5 > raises questions of maintenance going forward and whether all requirements > are met, whilst just adopting > the apps/HMI (I realise I am probably simplifying there) means masking out > parts for it to work on [1]. > > [1] https://github.com/meta-qt5/meta-qt5 > > Regards > > Steve > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstreif at jaguarlandrover.com Tue Jun 14 20:40:35 2016 From: rstreif at jaguarlandrover.com (Streif, Rudolf) Date: Tue, 14 Jun 2016 11:40:35 -0700 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: <49397B5F-B6D3-4C6C-909A-D88B028C3AAA@qt.io> References: <5760083D.7040702@gmail.com> <49397B5F-B6D3-4C6C-909A-D88B028C3AAA@qt.io> Message-ID: Hi Louai, > In the interest of avoiding fragmentation, I would like to invite > interested parties to work with us to make sure that there is one place > that provides high-quality recipes for these components. > > These components are included in our newly-public meta-boot2qt layer: > http://code.qt.io/cgit/yocto/meta-boot2qt.git/ > The README provides a good overview: > http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/README > > Is this based on "Qt for Device Creation" ( http://www.qt.io/qt-for-device-creation/)? At least the README mentions it. A while ago I wanted to give Qt for Device Creation a try for a hobby project but it seems to be commercially licensed only and there was only a 30 day free trial available. That still seems to be the case according to the website. Could you please clarify the licensing? It looks as if the layer itself is GPLv3-licensed. What about the boot2qt components? > meta-boot2qt builds on meta-qt5 to provide amongst other things more up to > date versions of Qt [1] and the above automotive packages [2]. It includes > a poky-based reference distro, but the recipes can certainly be used > independently. > > meta-boot2qt also provides support for a lot of devices. Currently this > includes the i.MX6, i.MX7, Rcar Gen 2, Raspberry Pi 1/2/3, Jetson > Pro/Tegra, VirtualBox, Intel. The full list can be seen in our layer init > script [3]. > > The layer is developed in the open through Qt Code Review (i.e. gerrit) > [4]. I am very happy to see the wide-spread interest in these components. > We welcome people to work with us to establish one high-quality, canonical > upstream for the recipes. > > Looks like it is a fully distro layer. I will give it a shot. Cheers, Rudi > Cheers, > Louai > > [1] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/qt5 > [2] > http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/automotive > [3] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/b2qt-init-build-env > [4] https://codereview.qt-project.org > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- *Rudolf J Streif* System Architect - Open Source Initiative Open Source Technology Centre *M:* +1.619.631.5383 *Email:* rstreif at jaguarlandrover.com UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR US: 1419 NW 14th Ave, Portland, OR 97209 jaguar.com | landrover.com ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologise for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tuukka.turunen at qt.io Wed Jun 15 06:47:51 2016 From: tuukka.turunen at qt.io (Tuukka Turunen) Date: Wed, 15 Jun 2016 04:47:51 +0000 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com>, Message-ID: Hi, Upstream meta-qt5 is used to the extent possible and all changes to it are actively pushed upstream. However, we want to use the latest Qt, thus minor modifications. Intention is not to fork meta-qt5. What we have should be considered rather a mirror. We are working with the meta-qt5 maintainers and contributing to it. We have actually even offered to make meta-qt5 an official part of the Qt Project. Currently it is still in github, but perhaps some day it can move under the Qt Project. PS. I am not a member of genivi lists, please forward the message if it is blocked. Yours, Tuukka ________________________________ L?hett?j?: Stephen Lawrence L?hetetty: ?15.?6.?2016 0:23 Vastaanottaja: phongtran Kopio: automotive-discussions at lists.linuxfoundation.org; genivi-projects at lists.genivi.org; automotive at qt-project.org Aihe: Re: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) Hi Phong, > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of phongtran > Sent: 14 June 2016 14:36 > To: automotive-discussions at lists.linuxfoundation.org > Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org > Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) > > Hi ALL, > > I would like to share the meta-qt5-ivi which provides qtapplicationmanager, > qtivi and qt-apps-neptune-ui. > > The repo is on github here: > https://github.com/phongt/meta-qt5-ivi > > I applied this layer to AGL distro and It can start up QEMU x86-64 KVM > Ubuntu 14.04 host PC. > > Please refer README for detail: > https://github.com/phongt/meta-qt5-ivi/blob/dev/README > > I uploaded the images here: > > https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc& > usp=sharing > > I attached some screenshoots of Neptune UI. > > Please review and give your feedbacks. Looks interesting. Thank you for sharing. One question from reading the Readme. I see it does not use the existing meta-qt5 layer [1]. Whilst trying to avoid drawing you into politics could you summarise technically why your layer has its own base Qt 5 parts? From a quick look the two layers seem to have a somewhat different focus and you've provided recipes presumably for just what you need. I am not thinking so much about a feature by feature comparison but the practicalities about layer architecture and adoption. To give one example the Genivi Development Platform (GDP) uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5 raises questions of maintenance going forward and whether all requirements are met, whilst just adopting the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. [1] https://github.com/meta-qt5/meta-qt5 Regards Steve _______________________________________________ Automotive mailing list Automotive at qt-project.org http://lists.qt-project.org/mailman/listinfo/automotive -------------- next part -------------- An HTML attachment was scrubbed... URL: From agustin.benito at codethink.co.uk Wed Jun 15 14:26:34 2016 From: agustin.benito at codethink.co.uk (Agustin Benito Bethencourt) Date: Wed, 15 Jun 2016 14:26:34 +0200 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: <5761497A.7030000@codethink.co.uk> Hi, On 15/06/16 06:47, Tuukka Turunen wrote: > > Hi, > > Upstream meta-qt5 is used to the extent possible and all changes to it > are actively pushed upstream. However, we want to use the latest Qt, > thus minor modifications. Intention is not to fork meta-qt5. What we > have should be considered rather a mirror. > > We are working with the meta-qt5 maintainers and contributing to it. We > have actually even offered to make meta-qt5 an official part of the Qt > Project. Currently it is still in github, but perhaps some day it can > move under the Qt Project. > > PS. I am not a member of genivi lists, please forward the message if it > is blocked. forwarded > > Yours, > > Tuukka > ------------------------------------------------------------------------ > L??hett??j??: Stephen Lawrence > L??hetetty: ???15.???6.???2016 0:23 > Vastaanottaja: phongtran > Kopio: automotive-discussions at lists.linuxfoundation.org > ; > genivi-projects at lists.genivi.org > ; automotive at qt-project.org > > Aihe: Re: [Automotive] [agl-discussions] Introduce Qt IVI layer > (meta-qt5-ivi) > > Hi Phong, > >> -----Original Message----- >> From: automotive-discussions-bounces at lists.linuxfoundation.org >> [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On >> Behalf Of phongtran >> Sent: 14 June 2016 14:36 >> To: automotive-discussions at lists.linuxfoundation.org >> Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org >> Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) >> >> Hi ALL, >> >> I would like to share the meta-qt5-ivi which provides qtapplicationmanager, >> qtivi and qt-apps-neptune-ui. >> >> The repo is on github here: >>https://github.com/phongt/meta-qt5-ivi >> >> I applied this layer to AGL distro and It can start up QEMU x86-64 KVM >> Ubuntu 14.04 host PC. >> >> Please refer README for detail: >>https://github.com/phongt/meta-qt5-ivi/blob/dev/README >> >> I uploaded the images here: >> >>https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc& >> usp=sharing >> >> I attached some screenshoots of Neptune UI. >> >> Please review and give your feedbacks. > > Looks interesting. Thank you for sharing. > > One question from reading the Readme. I see it does not use the existing > meta-qt5 layer [1]. > Whilst trying to avoid drawing you into politics could you summarise > technically why your layer > has its own base Qt 5 parts? From a quick look the two layers seem to > have a somewhat different focus > and you've provided recipes presumably for just what you need. > > I am not thinking so much about a feature by feature comparison but the > practicalities about > layer architecture and adoption. To give one example the Genivi > Development Platform (GDP) > uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone > wanted to adopt your work > into GDP the question arises as to how best to do that. Adopting your > Qt5 layer instead for the base Qt5 > raises questions of maintenance going forward and whether all > requirements are met, whilst just adopting > the apps/HMI (I realise I am probably simplifying there) means masking > out parts for it to work on [1]. > > [1] https://github.com/meta-qt5/meta-qt5 > > Regards > > Steve > _______________________________________________ > Automotive mailing list > Automotive at qt-project.org > http://lists.qt-project.org/mailman/listinfo/automotive > > > _______________________________________________ > genivi-projects mailing list > genivi-projects at lists.genivi.org > https://lists.genivi.org/mailman/listinfo/genivi-projects > -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito at codethink.co.uk From tranmanphong at gmail.com Wed Jun 15 16:32:42 2016 From: tranmanphong at gmail.com (phongtran) Date: Wed, 15 Jun 2016 21:32:42 +0700 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: <5761670A.2000202@gmail.com> On 06/14/2016 10:05 PM, Jos? Bollo wrote: Hi Jos? Bollo, > Hi Phong, > > That is interesting. > > I see the file > https://github.com/phongt/meta-qt5-ivi/blob/dev/recipes-qt/qt5/qtwebengine_git.bbappend > Is it what is needed to compile qtwebengine with gcc5 > Yes, This is for fixing the compile error. > If yes, I think that it should be submitted in AGL upstream I checked meta-agl and meta-agl-demo. qtwebengine have not been used in AGL layers yet. Regards, Phong. > > Best regards > Jos? Bollo > > Jos? Bollo - Senior Software Engineer > www.iot.bzh > > > 2016-06-14 15:35 GMT+02:00 phongtran >: > > Hi ALL, > > I would like to share the meta-qt5-ivi which provides > qtapplicationmanager, qtivi and qt-apps-neptune-ui. > > The repo is on github here: > https://github.com/phongt/meta-qt5-ivi > > I applied this layer to AGL distro and It can start up QEMU x86-64 > KVM Ubuntu 14.04 host PC. > > Please refer README for detail: > https://github.com/phongt/meta-qt5-ivi/blob/dev/README > > I uploaded the images here: > > https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc&usp=sharing > > I attached some screenshoots of Neptune UI. > > Please review and give your feedbacks. > Thank you. > > Regards, > Phong. > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > From tranmanphong at gmail.com Wed Jun 15 16:56:24 2016 From: tranmanphong at gmail.com (phongtran) Date: Wed, 15 Jun 2016 21:56:24 +0700 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: References: <5760083D.7040702@gmail.com> Message-ID: <57616C98.5080703@gmail.com> On 06/14/2016 11:27 PM, Stephen Lawrence wrote: Hi Steve, > Hi Phong, > >> -----Original Message----- >> From: automotive-discussions-bounces at lists.linuxfoundation.org >> [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On >> Behalf Of phongtran >> Sent: 14 June 2016 14:36 >> To: automotive-discussions at lists.linuxfoundation.org >> Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org >> Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) >> >> Hi ALL, >> >> I would like to share the meta-qt5-ivi which provides qtapplicationmanager, >> qtivi and qt-apps-neptune-ui. >> >> The repo is on github here: >> https://github.com/phongt/meta-qt5-ivi >> >> I applied this layer to AGL distro and It can start up QEMU x86-64 KVM >> Ubuntu 14.04 host PC. >> >> Please refer README for detail: >> https://github.com/phongt/meta-qt5-ivi/blob/dev/README >> >> I uploaded the images here: >> >> https://drive.google.com/folderview?id=0B7oqqrcWpAYlZkx2NXFzcDB2Znc& >> usp=sharing >> >> I attached some screenshoots of Neptune UI. >> >> Please review and give your feedbacks. > > Looks interesting. Thank you for sharing. Thank for your feedback. > > One question from reading the Readme. I see it does not use the existing meta-qt5 layer [1]. This layer depends on meta-qt5. I have just tested this layer with AGL distro. AGL distro also use meta-qt5. So I put AGL distro as dependencies. > Whilst trying to avoid drawing you into politics could you summarise technically why your layer > has its own base Qt 5 parts? Do you mean this https://github.com/phongt/meta-qt5-ivi/blob/dev/recipes-qt/qt5/qtbase_git.bbappend ? If yes, this is for fixing the compile error of qtwayland. > From a quick look the two layers seem to have a somewhat different focus > and you've provided recipes presumably for just what you need. > > I am not thinking so much about a feature by feature comparison but the practicalities about > layer architecture and adoption. To give one example the Genivi Development Platform (GDP) > uses [1] for the base Qt 5 parts for its Qt based HMI. This layer also use [1]. > So if say someone wanted to adopt your work > into GDP the question arises as to how best to do that. > Adopting your Qt5 layer instead for the base Qt5 > raises questions of maintenance going forward and whether all requirements are met, whilst just adopting > the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. > > [1] https://github.com/meta-qt5/meta-qt5 > > Regards > > Steve > From tranmanphong at gmail.com Wed Jun 15 17:10:16 2016 From: tranmanphong at gmail.com (phongtran) Date: Wed, 15 Jun 2016 22:10:16 +0700 Subject: [Automotive] [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi) In-Reply-To: <747926A2-B3EF-4F20-BBDE-84C61D077B3C@qt.io> References: <5760083D.7040702@gmail.com> <747926A2-B3EF-4F20-BBDE-84C61D077B3C@qt.io> Message-ID: <57616FD8.2050900@gmail.com> On 06/15/2016 01:06 AM, Louai Al-Khanji wrote: Hi Louai Al-Khanji, >>> I would like to share the meta-qt5-ivi which provides qtapplicationmanager, >>> qtivi and qt-apps-neptune-ui. > > > >> I am not thinking so much about a feature by feature comparison but the practicalities about >> layer architecture and adoption. To give one example the Genivi Development Platform (GDP) >> uses [1] for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work >> into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5 >> raises questions of maintenance going forward and whether all requirements are met, whilst just adopting >> the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on [1]. > > > > Hi all, > > In the interest of avoiding fragmentation, I would like to invite interested parties to work with us to make sure that there is one place that provides high-quality recipes for these components. > > These components are included in our newly-public meta-boot2qt layer: http://code.qt.io/cgit/yocto/meta-boot2qt.git/ > The README provides a good overview: http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/README > Thank for your sharing. I have not known the meta-boot2qt before. I would like to share background of this layer (meta-qt5-ivi). I read the information in this page https://blog.qt.io/blog/2016/06/08/announcing-the-qt-automotive-suite/ I think It will be useful for AGL or Genivi, if there has a layer which supports the Qt application manager and Qt IVI API. So I decided to create this layer for feasibility checking on AGL distro. > meta-boot2qt builds on meta-qt5 to provide amongst other things more up to date versions of Qt [1] and the above automotive packages [2]. It includes a poky-based reference distro, but the recipes can certainly be used independently. > > meta-boot2qt also provides support for a lot of devices. Currently this includes the i.MX6, i.MX7, Rcar Gen 2, Raspberry Pi 1/2/3, Jetson Pro/Tegra, VirtualBox, Intel. The full list can be seen in our layer init script [3]. > > The layer is developed in the open through Qt Code Review (i.e. gerrit) [4]. I am very happy to see the wide-spread interest in these components. We welcome people to work with us to establish one high-quality, canonical upstream for the recipes. > > Cheers, > Louai > > [1] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/qt5 > [2] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/recipes-qt/automotive > [3] http://code.qt.io/cgit/yocto/meta-boot2qt.git/tree/b2qt-init-build-env > [4] https://codereview.qt-project.org > > From richard.pannek at pelagicore.com Fri Jun 17 14:55:53 2016 From: richard.pannek at pelagicore.com (Richard Pannek) Date: Fri, 17 Jun 2016 14:55:53 +0200 Subject: [Automotive] QmlLive patch: Add new app icon, .desktop file and make install Message-ID: Hi, I am using QmlLive (http://code.qt.io/cgit/qt-apps/qmllive.git/) on Linux and there is no make install, nor a real app icon or .desktop file, so I couldn't install it and had to start it from the terminal which isn't quite optimal. I made some small changes to make installing on Linux possible, once those are accepted I will make a Arch Linux AUR package too, and someone else will be able to make deb packages and rpm packages. I also added a new app icon I got from Johan Thelin, who also gave the permission to use it, it's nothing special but at least a normal app icon. I don't have a mac, so I wasn't able to add this icon for the mac version, nor to the Windows version, perhaps there is someone who can do that too, I added the original icon as a svg file too. /Richard Richard Pannek tel:+46723948758 -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-new-app-icon-.desktop-file-and-make-install.patch Type: text/x-patch Size: 540173 bytes Desc: not available URL: From volker.krause at kdab.com Tue Jun 21 10:26:47 2016 From: volker.krause at kdab.com (Volker Krause) Date: Tue, 21 Jun 2016 10:26:47 +0200 Subject: [Automotive] QmlLive patch: Add new app icon, .desktop file and make install In-Reply-To: References: Message-ID: <4381766.XtCTFKQEfo@vkpc19> Hi, this looks sensible to me, could you submit this via Qt Gerrit please? That would make review easier and integration possible. Thanks! Volker On Friday 17 June 2016 14:55:53 Richard Pannek wrote: > Hi, > > I am using QmlLive (http://code.qt.io/cgit/qt-apps/qmllive.git/) on > Linux and there is no make install, nor a real app icon or .desktop > file, so I couldn't install it and had to start it from the terminal > which isn't quite optimal. > > I made some small changes to make installing on Linux possible, once > those are accepted I will make a Arch Linux AUR package too, and > someone else will be able to make deb packages and rpm packages. > > I also added a new app icon I got from Johan Thelin, who also gave the > permission to use it, it's nothing special but at least a normal app > icon. I don't have a mac, so I wasn't able to add this icon for the > mac version, nor to the Windows version, perhaps there is someone who > can do that too, I added the original icon as a svg file too. > > /Richard > > > Richard Pannek > tel:+46723948758 -- Volker Krause | volker.krause at kdab.com | Director Automotive KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. +49-30-521325470 KDAB - The Qt Experts -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4664 bytes Desc: not available URL: