[OE-core] [Openembedded-architecture] Future of sato and X in oe-core

[Mark Hatle]

On 2/11/20 8:01 AM, Alexander Kanavin wrote:
> 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.
> 
> Alex
> 
> On Tue, 11 Feb 2020 at 14:57, Alexander Kanavin <alex.kanavin at gmail.com
> <mailto:alex.kanavin at gmail.com>> wrote:
> 
>     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.

I don't think an example/reference UI is useful -- OTHER THEN -- we need a way
to test that the framework(s) that are provided are functional.  So lets, assume
Wayland/Weston combo..  we still need something that can use the mouse, show
that the cursor is being drawn properly, clicks are registered, etc etc etc..

I do think that we need to include a graphical framework (X.org, wayland/weston
combo, etc..) as well as a basic set of examples that can be used to verify that
they are working properly.

There is a secondary 'problem' which I see more as a business issue then a
technical one, everyone wants to have a way to 'demo the OpenEmbedded'.  It's
pretty hard to demo a build system, so they like to have a device that boots
quickly and goes to something graphical that shows it's "working".

--Mark

>     Alex
> 
>     On Tue, 11 Feb 2020 at 14:53, Adrian Bunk <bunk at stusta.de
>     <mailto:bunk at stusta.de>> wrote:
> 
>         On Tue, Feb 11, 2020 at 01:49:27PM +0100, Alexander Kanavin wrote:
>         >...
>         > - matchbox is reliant on gtk3 (to be obsoleted by gtk4 this year), and
>         does
>         > not have a Wayland compositor. Yocto project does not have the
>         resources to
>         > do the gtk4 port, or add a compositor.
>         >
>         > - no 'lightweight Wayland compositor with a desktop/launcher experience"
>         > has emerged in the open source space; I think the only realistic choice at
>         > the moment is the reference compositor Weston which provides a blank
>         > desktop with ability to open terminal windows.
>         >
>         > So the way I think things should be going (seeking opinions/inputs of
>         > course):
>         >...
>         > - oe-core continues to support and runtime-test X for as long as possible;
>         > for this a new image (say, 'core-image-sato-xorg') is created which will
>         > provide matchbox under X. However, once upstream bitrot sets in, and pain
>         > threshold is exceeded, this will be removed and/or relegated to a legacy
>         > layer.
>         >
>         > Thoughts?
> 
>         matchbox made sense at a time when you could go into a shop and buy an
>         internet tablet with Linux running on 256 MB flash with 256 MB RAM.
> 
>         Part of the problem is that the only remaining usage of this branch
>         of matchbox development seems to be as example UI for Yocto.
> 
>         For matchbox/sato I am wondering whether replacing it with parts of
>         meta-xfce from meta-openembedded would be a good way forward.
> 
>         Upstream Xfce still seems to be 2-3 years away from gtk4 and Wayland
>         support, but at the point where supporting X might become a problem
>         this should be available.
> 
>         Xfce was my first thought as replacement since it appears to be
>         well-maintained in meta-openembedded, no strong opinion whether
>         it is actually the best option.
> 
>         > Regards,
>         > Alex
> 
>         cu
>         Adrian
> 
> 
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>