[OE-core] GUI based images

[Paul Eggleton]

On Wednesday, 10 May 2017 11:09:59 PM NZST Alexander Kanavin wrote:
> On 05/10/2017 01:55 PM, Paul Eggleton wrote:
> > I make no secret of it - I am a Qt supporter. I'm willing to be convinced
> > that's not the right answer, though, if there are solid arguments.
> > However, if you'll excuse my paraphrasing, "it's not in OE-Core and can't
> > be, therefore we should just ignore it" isn't a case against it, it's a
> > logistical issue. We could easily get past that by bringing meta-qt5 into
> > poky as we do with OE-Core, or even just adding it to the build
> > configuration as needed.
> 
> That's not what I'm saying. I'm saying that for people who want a 
> 'reference UI for real products' and have no problem with Qt, we should 
> officially endorse meta-b2qt.
> 
> Seriosuly. They have a wayland compositor, and an app launcher, and a 
> set of embedded-specific demos, and it's written and tested by 
> specialists with an explicit target of making it easy to make products. 
> And it's open source with optional commercial support. In that light, 
> there is no sense whatsoever in solving the same problem in oe-core, poorly.

If that works then great! By all means let's test it and endorse it. At the 
moment we barely even acknowledge it's existence - it's not even in the layer 
index (though that is generally up to the layer maintainer, we can certainly 
encourage them to submit it.)

> > If we keep Sato effectively on life support as we have done up until now,
> > then it'll never get solved, and in the mean time we are presenting
> > something that is frankly woefully outdated which we have to maintain
> > entirely by ourselves.
> 
> Sato is not a reference UI, and has no pretensions of being that. It's 
> strictly an engineering UI, which is a different thing, and it's very 
> useful in that capacity.

You and I might understand that, but someone coming to the project fresh 
won't, mainly because we've never officially stated that anywhere. The only 
mention of anything like it is in fact the opposite - in the development 
manual we state "The Yocto Project ... also features the Sato reference User 
Interface, which is optimized for stylus-driven, low-resolution screens.". 
Granted, that statement is probably as old as Sato itself, but I think it 
speaks to how organised our messaging is on this topic.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre