Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Max Krummenacher <max.oss.09@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	Khem Raj <raj.khem@gmail.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: GUI based images
Date: Tue, 09 May 2017 21:43:38 +0200	[thread overview]
Message-ID: <1494359018.2459.2.camel@gmail.com> (raw)
In-Reply-To: <9779c7ca-6b12-a4d8-9fe4-c23c950ccfa3@linux.intel.com>

Am Dienstag, den 09.05.2017, 11:10 +0300 schrieb Alexander Kanavin:
> On 05/09/2017 01:50 AM, Khem Raj wrote:
> > A general usecase is that someone takes the reference and tweaks it to
> > meet the needs of a product quickly. For such usecases, it would be good to
> > consider the most widely used UI framework in embedded space. I
> > personally don't know how much sato is deployed but QT based systems
> > are quite widely deployed as far as I know. I think users can drive maximum
> > out of the testing and stabilization we do if they were using the reference
> > software as much as possible.
> 
> Qt itself does not provide a UI, so we would need to find an appropriate 
> qt-based replacement for Sato that has the same characteristics and is 
> suitable as an 'engineering UI'. What is your suggestion for that?
> 
> I personally think meta-qt5 works fine; it's only missing a reference UI 
> environment. Why not add LxQt to that layer?
> 
Andreas already has those recipes in meta-qt5-extra:
https://layers.openembedded.org/layerindex/recipe/39614/

And for those who want a look at LXDE:
http://git.toradex.com/cgit/meta-lxde.git/tree/recipes-lxde/packagegroup/packagegroup-lxde-extended.
bb?h=master

Max

> 
> Alex


      reply	other threads:[~2017-05-09 19:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 10:51 GUI based images Belal, Awais
2017-05-08 11:33 ` Jussi Kukkonen
2017-05-08 11:39   ` Alexander Kanavin
2017-05-08 22:15     ` Paul Eggleton
2017-05-09  8:05       ` Alexander Kanavin
2017-05-09  8:44         ` Alex J Lennon
2017-05-09  9:18           ` Ian Arkver
2017-05-09  9:30             ` Alexander Kanavin
2017-05-09  9:31               ` Burton, Ross
2017-05-09  9:19           ` Alexander Kanavin
2017-05-09 11:17           ` Mike Looijmans
2017-05-09  9:24       ` Burton, Ross
2017-05-09 20:19         ` Khem Raj
2017-05-09 20:39           ` Alexander Kanavin
2017-05-09 20:59             ` Khem Raj
2017-05-09 21:03             ` Paul Eggleton
2017-05-09 22:27               ` Philip Balister
2017-05-10  9:31               ` Alexander Kanavin
2017-05-10 10:55                 ` Paul Eggleton
2017-05-10 11:09                   ` Alexander Kanavin
2017-05-10 20:15                     ` Paul Eggleton
2017-05-11  7:43                       ` Alexander Kanavin
2017-07-17 12:32                     ` Jussi Kukkonen
2017-05-11  7:53         ` Alexander Kanavin
2017-05-15 12:36           ` Jussi Kukkonen
2017-05-15 15:56             ` Khem Raj
2017-05-08 11:43   ` Burton, Ross
2017-05-08 11:47     ` Alexander Kanavin
2017-05-08 15:18       ` Belal, Awais
2017-05-08 22:50     ` Khem Raj
2017-05-09  8:10       ` Alexander Kanavin
2017-05-09 19:43         ` Max Krummenacher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1494359018.2459.2.camel@gmail.com \
    --to=max.oss.09@gmail.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox