Age | Commit message (Collapse) | Author | Files | Lines |
|
renderAppToAreaAllowed.
Background is that an application wants to know if it is allowed to be rendered before it creates its own surface.
If it is not allowed, it does not need to allocate resources.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Hardcoded:
nav: nav@0.1
media: media@0.1
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Add new signal surfaceVisibilityChanged to homescreen and windowmanager API.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
This function can be used to request, if it is allowed to render a surface in a layout area in preparation of the real renderSurfaceToArea command. This call will not change anything, it is only a request.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Change parameter for renderSurfaceToArea.
Remove getLayoutRenderAreaForSurfaceId.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Only one Layout for CES2017 needed.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
-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>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Change-Id: I2d5eb487b5dc5f494ce21c7d70bb5597bc18e12e
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Change-Id: Ifa30ae67b383e99a190f9e0cd590ee8133bacf65
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
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>
|
|
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>
|
|
HomeScreen, one for apps, one for popups.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Initial implementation to show the idea. Also availabale a sample app that uses the new lib. The lib uses the GNU D-Bus lib.
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
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>
|
|
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>
|
|
- 3 demo color schemes included
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
|
|
06/24/2016
- reworked status bar
- reviewed D-Bus interfaces, now using signals instead of methods for day/night mode
- created new home screen simulator app
- license changed to Apache 2.0
- put D-Bus introspections in one central place
- disabled "only one instance allowed" for development
|