<div dir="ltr">Specifically (sorry for the rapid-followup), I think the main value proposition of core is integration and testing of various language toolchains and core libraries. UIs in embedded space can mean pretty much anything, and so I'd leave that to specialised layers.<div><br></div><div>Alex</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Feb 2020 at 14:57, Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>The question is: what are the use cases for an 'example/reference UI'? Why have one at all at this point? Remember, the core project is severely under-staffed and we need to commit our limited resources wisely.</div><div><br></div><div>Alex</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Feb 2020 at 14:53, Adrian Bunk <<a href="mailto:bunk@stusta.de" target="_blank">bunk@stusta.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On Tue, Feb 11, 2020 at 01:49:27PM +0100, Alexander Kanavin wrote:<br>
>...<br>
> - matchbox is reliant on gtk3 (to be obsoleted by gtk4 this year), and does<br>
> not have a Wayland compositor. Yocto project does not have the resources to<br>
> do the gtk4 port, or add a compositor.<br>
> <br>
> - no 'lightweight Wayland compositor with a desktop/launcher experience"<br>
> has emerged in the open source space; I think the only realistic choice at<br>
> the moment is the reference compositor Weston which provides a blank<br>
> desktop with ability to open terminal windows.<br>
> <br>
> So the way I think things should be going (seeking opinions/inputs of<br>
> course):<br>
>...<br>
> - oe-core continues to support and runtime-test X for as long as possible;<br>
> for this a new image (say, 'core-image-sato-xorg') is created which will<br>
> provide matchbox under X. However, once upstream bitrot sets in, and pain<br>
> threshold is exceeded, this will be removed and/or relegated to a legacy<br>
> layer.<br>
> <br>
> Thoughts?<br>
<br>
matchbox made sense at a time when you could go into a shop and buy an<br>
internet tablet with Linux running on 256 MB flash with 256 MB RAM.<br>
<br>
Part of the problem is that the only remaining usage of this branch<br>
of matchbox development seems to be as example UI for Yocto.<br>
<br>
For matchbox/sato I am wondering whether replacing it with parts of<br>
meta-xfce from meta-openembedded would be a good way forward.<br>
<br>
Upstream Xfce still seems to be 2-3 years away from gtk4 and Wayland <br>
support, but at the point where supporting X might become a problem<br>
this should be available.<br>
<br>
Xfce was my first thought as replacement since it appears to be <br>
well-maintained in meta-openembedded, no strong opinion whether<br>
it is actually the best option.<br>
<br>
> Regards,<br>
> Alex<br>
<br>
cu<br>
Adrian<br>
</blockquote></div></div>
</blockquote></div>