[OE-core] GUI based images

[Jussi Kukkonen]

I had a look at b2qt earlier and Alex asked me to share on list as well so
I'll resurrect this thread from May...

On 10 May 2017 at 14:09, Alexander Kanavin <
alexander.kanavin at linux.intel.com> 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.


My verdict after a bit of testing and some light digging at the sources:
Very cool demo, vastly better than Sato for "Trade show demo unit" use case
(although the current content is naturally just Qt marketing). It does not
seem useful as Sato-the-QA-platform replacement and I would be wary of
suggesting it for any product use without caveats: my worry is the
maintenance status of the DE components.

Some details:
* Some of the "Desktop Environment" components are possibly not meant for
production use: e.g. the wayland compositor/WM does not seem completely
finished, either from feature or polish POV. It's even called
"democompositor". The last real code change in the relevant repo was in Feb
2016. For a single app use case this might not matter.
* It wouldn't work as a generic desktop (needs launcher specific files per
application)
* That wouldn't be so bad but the only app they include is the browser, the
rest are ads or demos (browser admittedly is very nice)

Jussi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170717/7ca9065c/attachment-0002.html>