aboutsummaryrefslogtreecommitdiffstats
path: root/WindowManager
AgeCommit message (Collapse)AuthorFilesLines
2016-12-18Support scaled output for non-FHD screenTadao Tanikawa1-4/+16
This is a quick hack supporting scaled output to fit various monitors which has not FHD screen resolution. (Especially useful for running CES2017 demo on QEMU) - Layer - source rectangle is 1080x1920 - destination rectangle is variable to fit screen resolution - Surface - source rectangle is based 1080x1920 - destination rectangle is based 1080x1920 - From application view - screen size is always 1080x1920 and does not need to care about phsycial screen size This change enables scaled output which changes the size according to the ratio of source and destination region of homescreen layer. This patch doesn't resolve an issue, 'CES2017 demo keep blank screen after booting on some platform (QEMU, Raspberry Pi3, MinnowMax)'. (Workaround: just run any weayland client application such as 'LayerManagerControl', 'qmlscene', or weston example like 'weston-flower', then it breaks blank screen) Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
2016-12-16Add parameter "quiet" to suppress outputsBocklage, Jens1-0/+13
This will disable all debug outputs. All! Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-12-16Add app parameter to set display idBocklage, Jens3-7/+22
On systems with more then one display, you may want to set the display that will be managed. The default display is 0. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-12-16Make compilable on non HAVE_IVI_LAYERMANAGEMENT_API systemsBocklage, Jens1-2/+11
No functional changes Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-12-15Fix management of screenTadao Tanikawa1-8/+5
WindowManager can support signle screen only, so far. CAUTION: To apply this change for porter board, LVDS-1 output should be disabled first. (see Changes 7637 for detail) https://gerrit.automotivelinux.org/gerrit/#/c/7637/ Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
2016-12-14Fix and improve switching applicationsTadao Tanikawa2-34/+184
v2: (Tadao Tanikawa) Minor fixed pointed by reveiw and organize debug message v1: (Tadao Tanikawa) Quick hack to fix and improve switching applications. Changes: * Improve management of layers and surfaces Previously single layer was shared among all applications, now each application has its own layer. * Improve showing / hiding applications Previously to show/hide application, surfaces are added or removed everytime, but it's slow. Now reordering layers controls showing/hiding applications, it much faster. * Shortcut icons whose application is not installed no longer cause issue to switch apps. Caution: This patch is very quick hack, and many old codes which regarding to management surfaces are disabled, so there may be unnoticed degraded. Change-Id: I69494213b0d1b169558f3d792ebecf414caccacc Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
2016-12-12Hack to fix issue of switching appsTadao Tanikawa2-39/+51
To switching between apps, controlling surface's visiblity (on/off) does not work as intended. It looks work well to set render order of layers properly. TODO: switching between apps and navigation still doesn't work. For develop, navigation icon is assgined to 'controls@0.1' and now, controls app doesn't make any wl_surfaces (don't know why). Probably this causes issue switching between apps <-> navigation. Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
2016-12-08Disable verbose output of systems service fileBocklage, Jens1-1/+0
This is not needed in general Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-12-07Update install path in systemd unit filesScott Murray1-1/+1
The application is now installed in /usr/AGL/homescreen instead of in /usr/AGL/HomeScreen, update the systemd unit files to match. Signed-off-by: Scott Murray <scott.murray@konsulko.com>
2016-12-07Improve layer- and surface handlingBocklage, Jens2-68/+64
Still fighting with ilm API Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-25Arrange the surface z-order in the layerv0.6.3Bocklage, Jens1-1/+13
Using ilm_layerSetRenderOrder to set the order of the surfaces inside the layer. This is neccessary to show the surfaces on the screen. Resolves: #SPEC-333 Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-24Enable automcatic startup of Homescreen appBocklage, Jens2-14/+19
HomeScreen and its depending apps are started by default using systemd user session. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-23Use 4 layer instead of 3Bocklage, Jens1-1/+1
This fixes a typo where only three of the available four layers were shown on the screen. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-22fix typoTasuku Suzuki1-2/+2
Change-Id: I11b6b535c2587c5e61dfb17c8cb56f2554e06c06 Signed-off-by: Tasuku Suzuki <tasuku.suzuki@qt.io>
2016-11-21remove QMAKE_CLEAN += -r * from project filesTasuku Suzuki1-5/+0
use $ make distclean if you want to clean binaries and Makefile Change-Id: I4f9af670c8625f48a0f9f77d31117d2a1a1cbb22 Signed-off-by: Tasuku Suzuki <tasuku.suzuki@qt.io>
2016-11-21check ivi-layermanagement-api availabilityTasuku Suzuki3-13/+14
replace #ifdef __arm__ with a definition that comes from availability test Change-Id: Id9fa4baefcc9f38acd3e98d40054040fc69029c6 Signed-off-by: Tasuku Suzuki <tasuku.suzuki@qt.io>
2016-11-21cleanup project filesTasuku Suzuki1-10/+3
Change-Id: I4d605d97d050fb60e1fef749926cb1b92071782e Signed-off-by: Tasuku Suzuki <tasuku.suzuki@qt.io>
2016-11-21introduce interfaces.priTasuku Suzuki1-3/+1
Change-Id: I3649d5275b9da71feb216eb70c9d9fda73507d69 Signed-off-by: Tasuku Suzuki <tasuku.suzuki@qt.io>
2016-11-17Set surface source rectanglge on CONFIGURED event.Bocklage, Jens1-0/+11
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-17Add initial systemd service files.Bocklage, Jens1-0/+15
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-11Add Nav and Media app to control bar.20161111_preCESIntegrationWorkshopBocklage, Jens1-1/+1
Hardcoded: nav: nav@0.1 media: media@0.1 Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-11Add new layer WINDOWMANAGER_LAYER_HOMESCREEN_OVERLAY.Bocklage, Jens2-3/+30
Add new signal surfaceVisibilityChanged to homescreen and windowmanager API. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-09Fix for AppInfo member initialization.Bocklage, Jens1-2/+4
Only one Layout for CES2017 needed. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-08Pushed some versions to 0.6.0v0.6.0Bocklage, Jens1-1/+1
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-08-Make the SampleNav app yellow.Bocklage, Jens2-0/+77
-Preparation for the new ApplicationFramework binding. The App Framework provides more information. --Adding afm D-Bus-interface introspection --Updating the AppInfo datatype to hold the new data: The application info consists of: string id; string version; int width; int height; string name; string description; string shortname; string author; string iconPath; -When pressing the AppLauncher Button or the Settings Button, the app layer is hidden. --Therefore, shideLayer and showLayer is introduced in the WindowManager API -If an application does not create its surface instantly, the HomeScreen retries to show the surface related to the pid. -New WindowManager function deleteLayoutById -Implement the complete HomeScreen API in the libhomescreen Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-04Fix for pid and surface handling.Bocklage, Jens2-0/+19
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-03New concept of dynamically placing surfaces in static defined layout areas.v0.4.0Bocklage, Jens1-1/+1
This is useful if an application wants to render more than one surface. By default, one surface is placed in one layout render area. With the new homescreen.xml introspection, apps can place their surfaces as they wish (limited to the boundries of the assigned layou render area!). The functionality is not fully implemented, but the shared lib already provides the interface. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-03HomeScreen main surface has to have the surface id 1000!Bocklage, Jens2-59/+23
Use QT_IVI_SURFACE_ID=1000 QT_WAYLAND_SHELL_INTEGRATION="ivi-shell" ./HomeScreen & to launch HomeScreen. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-03HomeScreen is now visible independent of the Layout set.Bocklage, Jens1-9/+17
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-02New layer management in WindowManager. Three layers are created. One for the ↵Bocklage, Jens3-237/+283
HomeScreen, one for apps, one for popups. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-26Implement toggle full screen mechanism.Bocklage, Jens2-3/+28
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-26All apps print their app name and version on launch.Bocklage, Jens1-0/+2
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-21README cleanupBocklage, Jens1-15/+0
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-18WindowManager now handles application surfaces by its pids.Bocklage, Jens3-61/+171
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-09-30Implementing app launch and app surface control workflow. Using ↵Bocklage, Jens5-158/+338
WindowManager to control layer and surfaces (ongoing). Defining three layouts. Adding combobox selection feature to popup widget. Known issue: IVI-shell is currently disabled in AGL due to issues (porting to Yocto 2.1.1). Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-08-05Using the Tizen application manager to receive information about installed ↵v0.2.0Bocklage, Jens7-0/+591
apps and to launch apps. This acts as a template for other app framework adoptions. Using the weston ivi shell to control surfaces. Using the input event manager to dispatch hard key inputs. This is a bigger update, so I increased the version number from 0.1.1 to 0.2.0. Some parts are under development. I created the components "WindowsManager" and "InputEventManager" because they are not defined in AGL right now. As soon as they are defined, we should switch to them. Find more information on the official wiki page: https://wiki.automotivelinux.org/homescreen Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>