summaryrefslogtreecommitdiffstats
path: root/interfaces/homescreen.xml
AgeCommit message (Collapse)AuthorFilesLines
2017-01-04Add 2017 to copyrightBocklage, Jens1-1/+1
Happy new year Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-16Change HomeScreen API function renderSurfaceToAreaAllowed to ↵Bocklage, Jens1-9/+10
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>
2016-11-11Add new layer WINDOWMANAGER_LAYER_HOMESCREEN_OVERLAY.Bocklage, Jens1-0/+11
Add new signal surfaceVisibilityChanged to homescreen and windowmanager API. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-11Add org.agl.homescreen function renderSurfaceToAreaAllowed.Bocklage, Jens1-0/+14
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>
2016-11-09Changes to org.agl.homescreen interfaceBocklage, Jens1-25/+4
Change parameter for renderSurfaceToArea. Remove getLayoutRenderAreaForSurfaceId. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-11-07New HomeScreen API calls getSurfaceStatus and getAllSurfacesOfProcess.Bocklage, Jens1-50/+74
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/+42
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-02New layer management in WindowManager. Three layers are created. One for the ↵Bocklage, Jens1-1/+1
HomeScreen, one for apps, one for popups. Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-31Generate docbook file for the homescreen.xml introspection file.Bocklage, Jens1-1/+13
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-10-26Implement toggle full screen mechanism.Bocklage, Jens1-2/+1
Signed-off-by: Bocklage, Jens <Jens_Bocklage@mentor.com>
2016-09-30Implementing app launch and app surface control workflow. Using ↵Bocklage, Jens1-0/+3
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, Jens1-0/+22
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>