Westeros compositor for Wayland and it is a replacement of Weston targeting towards embedded systems.

• Westeros is smalland simple.
• Being small, easier to understand and maintain.
• Caters to needs of embedded systems over traditional desktop computing.
• Shared library that provides an APIfor creating and operating a compositor.
• Use the included sample compositor app OR implement a custom compositor.
• Allows an application to create a Wayland display within itself to create what we call an embedded compositor.
• Main UI can then control application windowandlifecycle.

Westeros Use Case

Advantages of Westeros over Weston Compositor

There are two main attributes of Westeros that could make it a good choice,

First:

• Westeros is small and simple and it is for targets embedded systems
• It’s small code size makes it easier to understand and maintain
• it concentrates on functionality needed for embedded systems rather than trying to include features related to traditional desktop computing

Second:

• The functionality of Wayland composition is in a shared library that provides an API for creating and operating a compositor.
• One can use the included sample compositor app, or just use it as a reference for implementing a custom compositor.  
• A big advantage this brings is that it allows an application to create a Wayland display within itself to create what we call an embedded compositor.

A system could have a primary user interface which allows other third party applications to provide additional functionality such as Netflix, and the primary UI can control the size and position of the third party UI to provide seamless integration. If, on the other hand, one wants to implement a system where the user moves, resizes, minimizes, and maximizes various windows, does drag and drop operations etc., then Weston would be a more appropriate choice.