All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Arkver <ian.arkver.dev@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: GUI based images
Date: Tue, 9 May 2017 10:18:20 +0100	[thread overview]
Message-ID: <70344400-e36e-497e-e061-56821561c353@gmail.com> (raw)
In-Reply-To: <931ee9bc-a5cb-fcc2-278b-20a07731524d@dynamicdevices.co.uk>

On 09/05/17 09:44, Alex J Lennon wrote:
> 
> 
> On 09/05/17 09:05, Alexander Kanavin wrote:
>> On 05/09/2017 01:15 AM, Paul Eggleton wrote:
>>>> LXDE in particular is Gtk2 based, it's no longer being developed, and
>>>> has been superseded by LXQt. So it's a non-starter (and so is LXQt,
>>>> which should be clear from its name :).
>>>
>>> FWIW I think this is a little short-sighted. Why are we ruling out Qt 
>>> exactly?
>>
>> We would first have to agree that Qt5 belongs in oe-core with 
>> appropriate level of maintenance and QA, and that it's okay to add 
>> half an hour or more to the building time of a standard GUI image.
>>
>> From the screenshots of LxQT, it looks like yet another Win95 clone 
>> meant strictly for desktop use that would certainly scale poorly to 
>> small resolution screens. Who would be the target audience for it in 
>> the embedded space? For the purposes of 'engineering UI', Sato is 
>> fine, and we don't need something else.
>>
>> Alex
> 
> fwiw. I would love to be able to develop devices like those pictured 
> below, which I believe are based on Qt for Device Creation.
> 
> https://d33sqmjvzgs8hq.cloudfront.net/wp-content/uploads/2014/08/devices.png 
> 
> 
> ref: https://www.qt.io/qt-for-device-creation/
> 
> Cheers,
> 
> Alex
> 

They have their own meta-b2qt layer for that. See "Embedded 
documentation" and "Building Your Own Embedded Linux Image" from that
page.

It's not an OE-core thing, imho.

Regards,
Ian


  reply	other threads:[~2017-05-09  9:18 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 [this message]
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

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=70344400-e36e-497e-e061-56821561c353@gmail.com \
    --to=ian.arkver.dev@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.