summaryrefslogtreecommitdiffstats
path: root/app
AgeCommit message (Collapse)AuthorFilesLines
2021-02-01Tweak things to center the windowmarlin_12.90.0marlin/12.90.0lamprey_11.92.0lamprey_11.91.0lamprey/11.92.0lamprey/11.91.012.90.011.92.011.91.0Scott Murray2-1/+18
Add a onCompleted hook in Main.qml to set it's x and y coordinates to center the window, and rework instantiation of the qml in main.cpp so that the resulting x and y values can be queried and used in a call to set_window_props to actually position the window. Bug-AGL: SPEC-3784 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: I46e2dfac7c62c9afd379fd6bf7b7fa3277422cbc
2020-07-08app: Re-work the deactivation part in application_id_state eventkoi_10.93.0koi_10.92.0koi_10.91.0koi/10.93.0koi/10.92.0koi/10.91.0jellyfish_9.99.4jellyfish_9.99.3jellyfish_9.99.2jellyfish/9.99.4jellyfish/9.99.3jellyfish/9.99.29.99.49.99.39.99.210.93.010.92.010.91.0Marius Vlad1-20/+37
In commit 11b9762f115778 we've added some logic in place that would allow to start the application de-activated (that is hidden), as to avoid 'stealing' the input focus (hoovering the pointer over a surface will give that surface focus). alexa-viewer application would be started by default by the system and will be set 'invisible' (due to being a Qt app with the property set as visible: false), and most likely this might cause a bit of confusion for users. Also, by default, the compositor will display the application as soon as started. This patch re-works the de-activation part to handle a corner case, as in commit 11b9762f115778 we would send the de-activate request as a response in an event handler but it seems we can't guarantee that at that time the surface was indeed activated. So, instead of using application_id event, we use the application_id_state event, which guarantees that we were actually sending the de-activate request after we got the activate state event from the compositor. Bug-AGL: SPEC-3412 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ie50b8011700d258a899374176fb78dcd528f88c1
2020-06-24Add protocol remote role and bounding boxjellyfish_9.99.1jellyfish/9.99.19.99.1Marius Vlad4-7/+39
Bug-AGL: SPEC-3447 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Icdcd76a75177dd7dd20a3a4e69fa1b79edc5de8d
2020-06-24Deactivate ourselves the first time we startMarius Vlad1-10/+24
Fixes #SPEC-3412 Bug-AGL: SPEC-3412, SPEC-3447 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I3f2814fa88a0f27387889aacadd0849cd58b9b6a
2020-06-24agl-compositor: Adapt alexa-viewer to using the agl-shell-desktop protoMarius Vlad6-61/+434
Do not hide the app, for the time being. Bug-AGL: SPEC-3447 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I15e5f40b2d3864dd8e251f75b0a4ba05487c7649
2020-06-08replace qtappfw with qtappfw-voice-metadata packageRaquel Medina1-1/+1
Bug-AGL: SPEC-3390 Signed-off-by: Raquel Medina <raquel.medina@konsulko.com> Change-Id: I17491facf5cae7e129ab8a4c364d16724db732d1
2020-01-17Initial check-inicefish_8.99.5icefish/8.99.5halibut_8.0.6halibut_8.0.5halibut/8.0.6halibut/8.0.58.99.58.0.68.0.5halibutScott Murray8-0/+1116
A simple application that pops up to display the guimetadata responses from the voice capabilities API. It is currently considered to be Alexa specific, as it relies on the response templates provided by the Alexa voiceagent via the capabilities API, and there are no other voiceagents available to vet whether those template contents will be treated as a fixed part of the capabilities API. At the moment, only the two types of body template (BodyTemplate1 and 2) and the WeatherTemplate are handled, and rendering of the latter is only of the current day's weather. The application uses the onscreen role so that it can pop up above running applications. To drive the pop up behavior, a simple client is used to handle the guimetadata events from vshl-capabilities and show the window with the homescreen API. Filling in the template is handled with separate support from libqtappfw to provide the template data to Qt. Additionally, note that there currently is a hook for the navigation capability in the simple afb client to enable raising the navigation application when the setDestination capability is triggered. Once a better place to handle this is architected, it should be moved out of this application. Bug-AGL: SPEC-3110 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: Ifce9554b93d1e781283fd68f8e911a7010dd8cf0