Commit 71f9ee1d authored by eucan's avatar eucan Committed by eucan
Browse files

ivi-shell: don't use input panel implementation

input panel implementation puts contents of an
application, which uses input_method protocol,
on top of all other surfaces. It is not controllable
with ivi-layout interface.

This is not acceptable for an In-Vehicle Infotainment
platform. Because we have to ensure configured scenegraph
cannot be hijacked by any rogue application.

Therefore, I am removing input panel implementation

Signed-off-by: eucan's avatarEmre Ucan <>
parent 5a5cbc02
......@@ -359,10 +359,6 @@ shell_destroy(struct wl_listener *listener, void *data)
struct ivi_shell_surface *ivisurf, *next;
wl_list_for_each_safe(ivisurf, next, &shell->ivi_surface_list, link) {
......@@ -404,8 +400,6 @@ init_ivi_shell(struct weston_compositor *compositor, struct ivi_shell *shell)
weston_layer_init(&shell->input_panel_layer, compositor);
section = weston_config_get_section(config, "ivi-shell", NULL, NULL);
weston_config_section_get_bool(section, "developermode",
......@@ -498,13 +492,6 @@ wet_shell_init(struct weston_compositor *compositor,
shell->wake_listener.notify = wake_handler;
wl_signal_add(&compositor->wake_signal, &shell->wake_listener);
if (input_panel_setup(shell) < 0)
goto out;
shell->text_backend = text_backend_init(compositor);
if (!shell->text_backend)
goto out;
if (wl_global_create(compositor->wl_display,
&ivi_application_interface, 1,
shell, bind_ivi_application) == NULL)
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment