From: joakim@verona.se
To: Aiko Kyle <aikokyle@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, Lars Ingebrigtsen <larsi@gnus.org>,
Anand Tamariya <atamariya@gmail.com>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Multimedia dashboard in GNU Emacs
Date: Wed, 29 Dec 2021 14:34:18 +0100 [thread overview]
Message-ID: <87zgoj5ycl.fsf@tanaka.verona.se> (raw)
In-Reply-To: <CAPWcbYHsyc0siArxgi4jbAH86vE=GK6yjxvsAbQx2ZCW7Uwtcw@mail.gmail.com> (Aiko Kyle's message of "Tue, 28 Dec 2021 18:44:27 -0700")
Aiko Kyle <aikokyle@gmail.com> writes:
> On Sun, Dec 26, 2021 at 10:07 PM Po Lu <luangruo@yahoo.com> wrote:
>>
>> Anand Tamariya <atamariya@gmail.com> writes:
>>
>> > Do we have to necessarily use off-screen rendering? Are you referring
>> > to some problem with the scenario as in the attached pic? Can you
>> > elaborate?
>>
>> Yes, a single xwidget has to look and behave identically in every window
>> it is attached to.
>>
>
> You mean technically it has to given the way its implemented? There
> isn't some other reason why an xwidget has to behave this way?
It kind of has to, in order to preserve the way emacs behaves.
That is multiple views of the same buffer, and so on.
In the original xwidget branch there were some alternative behaviours
implemented as proof of concepts, and they worked to some degree, but
breaks the emacs paradigm, so they arent really all that useful IMHO.
There might also be some kind of experiment involving redirection of an
applications main window to an offscreen widget, that might be useful
for xwidget, but I'm not entirely sure.
--
Joakim Verona
joakim@verona.se
next prev parent reply other threads:[~2021-12-29 13:34 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 [this message]
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
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=87zgoj5ycl.fsf@tanaka.verona.se \
--to=joakim@verona.se \
--cc=aikokyle@gmail.com \
--cc=atamariya@gmail.com \
--cc=emacs-devel@gnu.org \
--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).