*** shoragan has quit IRC | 01:40 | |
*** shoragan has joined #automotive | 02:02 | |
*** shoragan has quit IRC | 02:36 | |
*** shoragan has joined #automotive | 02:38 | |
*** jluzny_ has joined #automotive | 03:58 | |
*** jluzny has quit IRC | 03:58 | |
*** anjumkaiser has joined #automotive | 04:39 | |
*** anjumkaiser has quit IRC | 06:00 | |
*** anjumkaiser has joined #automotive | 06:01 | |
*** mckoan|away is now known as mckoan | 06:47 | |
*** jobol has joined #automotive | 07:03 | |
*** jbpons has joined #automotive | 07:52 | |
*** anjumkaiser has quit IRC | 07:56 | |
*** vrubiolo has joined #automotive | 08:06 | |
*** _jbpons_ has joined #automotive | 08:28 | |
*** jbpons has quit IRC | 08:31 | |
*** vrubiolo has quit IRC | 08:33 | |
*** jbpons has joined #automotive | 08:33 | |
*** _jbpons_ has quit IRC | 08:36 | |
*** vrubiolo has joined #automotive | 08:36 | |
dl9pf | Hi ! | 08:39 |
---|---|---|
dl9pf | efeschiyan: ping | 08:40 |
*** kooltux_ has joined #automotive | 08:47 | |
*** jobol has left #automotive | 08:51 | |
*** _jbpons_ has joined #automotive | 09:13 | |
*** jbpons has quit IRC | 09:16 | |
*** jbpons has joined #automotive | 09:19 | |
*** _jbpons_ has quit IRC | 09:20 | |
*** dl9pf has quit IRC | 09:26 | |
*** dl9pf has joined #automotive | 09:26 | |
*** Newami has joined #automotive | 10:31 | |
*** boron has joined #automotive | 11:06 | |
dl9pf | hi boron | 11:07 |
*** boron has quit IRC | 11:37 | |
*** boron has joined #automotive | 11:43 | |
*** boron has quit IRC | 12:11 | |
*** boron has joined #automotive | 13:10 | |
*** _jbpons_ has joined #automotive | 13:13 | |
*** jbpons has quit IRC | 13:16 | |
*** jbpons has joined #automotive | 13:19 | |
*** _jbpons_ has quit IRC | 13:20 | |
*** boron has quit IRC | 14:04 | |
*** Newami has joined #automotive | 14:48 | |
*** Newami has quit IRC | 14:52 | |
jbpons | Hi everyone ! For onScreen app, is this documentation up to date ? https://docs.automotivelinux.org/docs/en/master/apis_services/reference/hmi-framework/ApplicationGuide.html#sequence | 15:14 |
mvlad | jbpons: you should still receive (those) events from libhomescreen/homescreen binding, but their superflous wrt window/surface switching. | 15:23 |
mvlad | They don't actually inform about wm purposes, but about handling/starting application(s). | 15:24 |
mvlad | Wrt to regular applications, you don't actually need any code that handles windows, that should be automatically taken care of. By 'regular', I mean applications that do not intended to display/activate other applications. | 15:27 |
jbpons | Ok but, if I understand, to display an app "onScreen" I need "onscreenapp" ? So I'm not in the 'regular' situation ? | 15:33 |
jbpons | My precise question is : can I install the "onscreenapp" and use the homescreen's method showOnScreen with "onscreenapp" as application_id ? | 15:35 |
mvlad | It's been a while since I've used that app, so I had to look what it did. I've used a sandbox branch to test out the pop-up/dialog feature that onscreen has. | 15:38 |
mvlad | For a more up-to-date similar feature I would look into alexa-viewer. | 15:38 |
mvlad | The sandbox for onscreen app is sandbox/mvlad/agl-compositor, but it might be stale at this point. | 15:39 |
jbpons | Ok ! Thank you for yours answers :) I will look at alexa-viewer | 15:40 |
mvlad | Sure, alexa-viewer should be pretty explanatory. Maybe it gives a better view on what you're trying to achieve overall. It is far from perfect, but onscreenapp had the 'bad' habbit of sending data between applications in a weird way (I think using libhomescreen or system-daemon?), and while you might still have that possibility, I'd advise against it. You need some dedicated binding I guess to | 16:03 |
mvlad | hang off the data which your pop-up/dialog would want to display. | 16:03 |
mvlad | better put, need a mechanism to transfer data to your pop-up/dialog window (which is actually an application). The moment that you have that information, you can display the pop-up/dialog. You can display it before ofc, I'm more talking about some signal/async machinery. That pretty much summarizes how alexa-viewer works, in a birds-eye view. Particular for alexa-viewer is that all of that is | 16:10 |
mvlad | baked in, it will 'activate' or 'hide' itself, not other pop-up/dialog window. | 16:10 |
jbpons | Ok thanks for all this information | 16:17 |
smurray | onscreenapp was sending json that described what buttons should be appear as an extra parameter in the showWindow call of the old homescreen binding | 16:22 |
*** kooltux_ has quit IRC | 16:32 | |
*** vrubiolo has quit IRC | 16:36 | |
*** jbpons has quit IRC | 16:45 | |
*** mckoan is now known as mckoan|away | 16:47 | |
*** nighcoder has quit IRC | 17:50 | |
*** Newami has joined #automotive | 19:46 | |
*** Newami has quit IRC | 19:50 | |
*** anjumkaiser has joined #automotive | 20:57 | |
*** anjumkaiser has quit IRC | 21:23 | |
*** kooltux_ has joined #automotive | 21:40 | |
*** kooltux_ has quit IRC | 21:50 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!