5 ms·
My understanding of how this works, mostly from reading commit messages and poking around the repo, is to add a wayland compositor/server to the aura component
by tmzt 10y ago
My understanding of how this works, mostly from reading commit messages and poking around the repo, is to add a wayland compositor/server to the aura component of chromium. Aura is the window manager, compositor, and render of ui items such as the task bar and status icons of ChromeOS. It looks like the Android portion is largely based on the same fork as ARC, with the rendering performed through Wayland. It also looks like a large number of Android APIs had to be reimplemented which may excacerbate the fragmentation problem.
- 0xFFC 10y agoCool , did they used Wayland? I didn't know that. It is quite fascinating, Wayland finds its actual place in industry. About API reimplantation, I do remember a little bit, you are correct, the guy in Google talk mentioned it is simultaneous development to Android and they are not using Android underlying technology on top of namespace,etc (Linux syscalls). I would love to read a blog post about this, and since your poked around in source code you are right person. So please, if you have any spare time, write a blog post.