Flutter apps are displayed full-screen

Close for Pike M1

This has been fixed, in octopus and master.

Some further updates on this front:

• for octopus I've added an additional patch which doesn't clear the activation area in all cases - the client can send alg_shell_destroy() at any time, but doesn't mean we should also clear that activation area. If we're racing with other clients that can interfere with it.

• for master, I've included the two patches in octopus + one more to give ini configuration file precedence over the agl_shell request that's doing the same thing.

For master this issue could've have happened because a) with the user session removal we no longer start the gRPC proxy – seems to be regression in master as I had to add that manually, and b) even if we start the gRPC proxy, the window is much smaller as agl_shell is setting up the activation area.

With the changes in place for octopus we are fallback to reading the ini configuragation file at ready() request time, but also fixes the underlying issue, similar to master.

I debated quite a lot to actually assert if we detect a empty activation area at ready() time, but that doesn't work that good with the master change to give the ini configuration file precedence over the agl_shell request.

If there's something that we can document with respect to options for someone stuck with a graphics toolkit where such integration might be quite difficult or impossible (where TBH, I'm not sure there's much we can offer), that seems like a worthwhile thing to expand on as well...

Some examples here would be useful, stuck with graphics toolkit like what?

I've added and to improve our documentation regarding agl-shell and the gRPC interface associated. Some of documentation already suggest what I've been saying here, but you're right, having a naked, simple shell client than can help users. Shouldn't we also include this native-shell-client closer to the compositor? This we could remove the "nothing is displayed on my screen without a shell client" issue, similar to how we have it for agl-vkm

Regarding backwards compatibility is this about that we had/have another private extension and now we're moving/migrating towards a gRPC interface, or is that from ivi-shell/wayland-ivi-extension to using agl-shell? How do I move my window to x, y positioning and be width and height dimension kind of question or, I used to do this using agl-shell-desktop how do I do it now?

For further extending and debugging capabilities there's . I sort of feel that SPEC targets more what people coming from ivi-shell expect, though there's overlap with the gRPC interface we're providing to users.