From: Aiko Kyle <aikokyle@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Anand Tamariya <atamariya@gmail.com>,
joakim@verona.se, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Multimedia dashboard in GNU Emacs
Date: Thu, 30 Dec 2021 19:39:34 -0700 [thread overview]
Message-ID: <CAPWcbYFUrvbMVHpOOBYW0b9yhaL0+iDCszr6YL_trh1cJq_t_A@mail.gmail.com> (raw)
In-Reply-To: <87ilv5mvxf.fsf@yahoo.com>
On Thu, Dec 30, 2021 at 5:59 PM Po Lu <luangruo@yahoo.com> wrote:
>
> Aiko Kyle <aikokyle@gmail.com> writes:
>
> > As I see. So in this idea, the entire webpage would be rendered in the
> > case of a xwidget webkit? That seems like it would be costly for
> > especially large webpages.
>
> WebKit in general tends to choke on large webpages, so I'm not too
> worried.
>
Are you actually thinking about implementing this idea?
> > Do you then plan on implementing other xwidget types besides the
> > webkit one? I think with respect to the UI, osr makes more sense for
> > other widget types like buttons.
>
> Yes, there will be a GStreamer widget: it will use multiple video sinks
> connected to a single tee, allowing for a source to be displayed in
> multiple windows without offscreen rendering.
>
I'll be interested to see how that integrates with the existing xwidget code.
> > I agree the offscreen rendering is more general, however it seems to
> > me to add significant complexity that would be unnecessary if the UI
> > for it doesn't require it. Especially since the one-to-one webkit
> > buffer-window paradigm already has to be accounted for on ns, where
> > osr isn't available.
>
> I consider that a bug, but I don't know enough about NS development to
> fix it.
According to the author of nsxwidget.m and their comment at the top of
the file, it's maybe not technically possible. I think rendering to
offscreen surfaces probably breaks assumptions the webkit developers
make, and the situation will likely only get worse as browsers are
increasingly hardware accelerated.
next prev parent reply other threads:[~2021-12-31 2:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 6:35 Multimedia dashboard in GNU Emacs Anand Tamariya
2021-12-24 9:46 ` Lars Ingebrigtsen
2021-12-24 10:03 ` Po Lu
2021-12-27 4:22 ` Anand Tamariya
2021-12-27 5:03 ` Po Lu
2021-12-29 1:44 ` Aiko Kyle
2021-12-29 13:34 ` joakim
2021-12-29 19:08 ` Aiko Kyle
2021-12-29 20:08 ` joakim
2021-12-29 23:39 ` Aiko Kyle
2021-12-30 1:02 ` Po Lu
2021-12-30 3:21 ` Aiko Kyle
2021-12-30 3:29 ` Po Lu
2021-12-30 4:18 ` Aiko Kyle
2021-12-30 4:48 ` Po Lu
2021-12-30 20:25 ` Aiko Kyle
2021-12-31 0:59 ` Po Lu
2021-12-31 2:39 ` Aiko Kyle [this message]
2021-12-31 3:38 ` Po Lu
2021-12-27 4:16 ` Anand Tamariya
2021-12-27 12:06 ` Lars Ingebrigtsen
2021-12-28 4:19 ` Richard Stallman
2021-12-28 5:41 ` Po Lu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPWcbYFUrvbMVHpOOBYW0b9yhaL0+iDCszr6YL_trh1cJq_t_A@mail.gmail.com \
--to=aikokyle@gmail.com \
--cc=atamariya@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).