<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>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...</div><div><br></div></div><div class="gmail_quote">On 10 May 2017 at 14:09, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 05/10/2017 01:55 PM, Paul Eggleton wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I make no secret of it - I am a Qt supporter. I'm willing to be convinced<br>
that's not the right answer, though, if there are solid arguments. However, if<br>
you'll excuse my paraphrasing, "it's not in OE-Core and can't be, therefore we<br>
should just ignore it" isn't a case against it, it's a logistical issue. We<br>
could easily get past that by bringing meta-qt5 into poky as we do with OE-<br>
Core, or even just adding it to the build configuration as needed.<br>
</blockquote>
<br></span>
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.<br>
<br>
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. </blockquote><div><br></div><div><div><div>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.</div><div><br></div></div><div>Some details:</div><div>* 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. <br></div><div>* It wouldn't work as a generic desktop (needs launcher specific files per application)</div><div>* 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)</div><div><br></div><div>Jussi</div><div><br></div></div></div></div></div>