On Sat, Mar 23, 2013 at 2:15 AM, Bill Spitzak wrote:
> Jonas Ådahl wrote:
>
>> There are two clients (A and B) that can communicate via some IPC
>> mechanism where A is the main process and B is a render process. B
>> renders to a surface and A decides its visibility and position. Below
>> follows
On Fri, Mar 22, 2013 at 5:06 PM, Jason Ekstrand wrote:
> Hi Jonas,
Hi Jason,
> I'm really starting to like the look of this. However there are
> still a few sticky spots. First: How do you plan to handle resizing in
> a sane way? Do you plan to do that entirely through the external IPC
> mecha
Jonas Ådahl wrote:
There are two clients (A and B) that can communicate via some IPC
mechanism where A is the main process and B is a render process. B
renders to a surface and A decides its visibility and position. Below
follows an example how foreign surfaces can be used.
1. Both A and B conn
Hi Jonas,
I'm really starting to like the look of this. However there are
still a few sticky spots. First: How do you plan to handle resizing in
a sane way? Do you plan to do that entirely through the external IPC
mechanism or have some sort of configure event that gets passed via
wayland? Also,
A foreign surface is a surface created given a handle associated with a
previously exported surface. A handle is a randomly generated unique
identifier that on the server can associate a handle with a surface.
The exported surface is a surface created as normal but exported via the
wl_foreign_surf
