Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: RFC: Web browsing and HTML in OE-Core
Date: Thu, 22 Aug 2013 15:04:55 +0100	[thread overview]
Message-ID: <1377180295.6762.19.camel@ted> (raw)

We've slowly been shaking out the definition of OE-Core and as part of
that we removed web and web-gtk which were the only browsers in there
and were admittedly a bit limited/broken.

There is no doubt that web technology has an increasingly important role
in the future and in embedded devices (e.g. kiosk type devices, digital
signs and so on).

With that in mind, I think some kind of HTML support in OE-Core is
important going forward. Equally, I dislike having things there which we
cannot test. I know some people have looked into this and it appears
midori is the best option for something with a small number of
additional dependencies. I therefore currently think this is something
we should make a decision to include since it gives us significantly
better coverage of things like webkit which are a already in the core
yet totally untested at present.

I'm open to opinions, equally we do need to make a decision on this soon
since we're nearly at the feature freeze point. Thoughts?

Cheers,

Richard





             reply	other threads:[~2013-08-22 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 14:04 Richard Purdie [this message]
2013-08-22 14:18 ` RFC: Web browsing and HTML in OE-Core Phil Blundell
2013-08-23 11:17   ` Richard Purdie
2013-08-23 15:56     ` Phil Blundell
2013-08-23 16:14       ` Richard Purdie
2013-08-23 17:03         ` Phil Blundell
2013-08-22 14:24 ` Samuel Stirtzel
2013-08-23 11:16   ` Richard Purdie
2013-08-22 17:24 ` Otavio Salvador

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=1377180295.6762.19.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox