From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: GStreamer xwidget
Date: Sat, 20 Nov 2021 16:05:07 +0800 [thread overview]
Message-ID: <87zgpzp80c.fsf@yahoo.com> (raw)
In-Reply-To: <E1moL0l-0005fN-Pu@fencepost.gnu.org> (Richard Stallman's message of "Sat, 20 Nov 2021 02:42:11 -0500")
Richard Stallman <rms@gnu.org> writes:
> > I would like to install the following change that introduces a
> > GStreamer-based media widget.
>
> > It depends on GStreamer, gst-plugins-base, and gst-plugins-good and is
> > thus a compile-time option.
> Before deciding whether to install this, we need to understand clearly
> what jobs it can do. What kinds of media does GStreamer stream?
The plugins that this change takes advantage of will only stream free
software, as it doesn't depend on gst-plugins-ugly or gst-plugins-bad.
> Which formats? Does GStreamer implement DRM?
I can't give a definitive list of formats, but the GStreamer plugins
this change will take advantage of only support free formats, consist
entirely of free code, and have a policy against implementing DRM.
> Is GStreamer 100% free ziyou software, with no exceptions?
GStreamer itself is a framework that is 100% free (as in freedom)
software. There are proprietary plugins that implement DRM, but they
are separate from GStreamer itself and the base and good plugins, and
Emacs will not use them even if present on a user's system.
> We also have to think about whether it is good or bad to introduce
> this nonmodularity. What is better about showing videos this way,
> rather than just launching vlc in another window?
People seem to want that in Emacs.
Thanks.
next prev parent reply other threads:[~2021-11-20 8:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee7cq2mu.fsf.ref@yahoo.com>
2021-11-19 2:51 ` GStreamer xwidget Po Lu
2021-11-19 4:01 ` T.V Raman
2021-11-19 4:21 ` Po Lu
2021-11-19 5:38 ` Lars Ingebrigtsen
2021-11-19 5:49 ` Po Lu
2021-11-19 6:19 ` Lars Ingebrigtsen
2021-11-19 6:37 ` Po Lu
2021-11-19 6:53 ` Lars Ingebrigtsen
2021-11-19 13:03 ` Eli Zaretskii
2021-11-19 13:07 ` Po Lu
2021-11-19 13:22 ` Eli Zaretskii
2021-11-19 13:33 ` Po Lu
2021-11-19 13:45 ` Eli Zaretskii
2021-11-20 5:07 ` Po Lu
2021-11-20 7:23 ` Eli Zaretskii
2021-11-20 7:27 ` Po Lu
2021-11-21 5:19 ` Richard Stallman
2021-11-21 6:53 ` Lars Ingebrigtsen
2021-11-22 4:31 ` Richard Stallman
2021-11-20 7:42 ` Richard Stallman
2021-11-20 8:05 ` Po Lu [this message]
2021-11-20 8:16 ` Lars Ingebrigtsen
2021-11-21 5:18 ` Richard Stallman
2021-11-21 5:27 ` Po Lu
2021-11-22 4:31 ` Richard Stallman
2021-11-22 4:41 ` Po Lu
2021-11-23 6:11 ` Richard Stallman
2021-11-23 7:07 ` Po Lu
2021-11-23 20:54 ` Richard Stallman
2021-11-24 0:32 ` Po Lu
2021-11-25 5:32 ` Richard Stallman
2021-11-25 8:13 ` Po Lu
2021-11-25 11:34 ` Alexandre Garreau
2021-11-27 4:09 ` Richard Stallman
2021-12-01 12:30 ` Dmitry Gutov
2021-12-01 17:53 ` Arthur Miller
2021-12-02 0:51 ` Po Lu
2021-12-02 2:47 ` chad
2021-11-27 4:08 ` Richard Stallman
2021-11-27 4:38 ` Po Lu
2021-11-28 4:24 ` Richard Stallman
2021-11-28 4:42 ` Po Lu
2021-11-28 8:04 ` Yuri Khan
2021-11-28 8:16 ` Po Lu
2021-11-29 3:02 ` Richard Stallman
2021-11-29 7:31 ` Yuri Khan
2021-11-29 7:44 ` Po Lu
2021-11-29 21:12 ` Richard Stallman
2021-11-30 1:38 ` Po Lu
2021-11-30 8:30 ` Yasushi SHOJI
2021-11-30 9:29 ` Po Lu
2021-11-30 10:30 ` Yasushi SHOJI
2021-12-01 7:04 ` Richard Stallman
2021-12-01 7:09 ` Po Lu
2021-11-30 4:09 ` Richard Stallman
2021-11-29 3:01 ` Richard Stallman
2021-11-29 3:12 ` Po Lu
2021-11-30 4:09 ` Richard Stallman
2021-11-30 4:36 ` Po Lu
2021-12-01 7:04 ` Richard Stallman
2021-11-23 6:11 ` Richard Stallman
2021-11-23 6:55 ` Po Lu
2021-11-24 4:28 ` Richard Stallman
2021-11-21 6:52 ` Lars Ingebrigtsen
2021-11-21 14:45 ` Arthur Miller
2021-11-23 6:09 ` Richard Stallman
2021-11-22 4:31 ` Richard Stallman
2021-12-01 7:07 ` Richard Stallman
2021-12-01 7:31 ` Po Lu
2021-12-01 8:30 ` Alexandre Garreau
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=87zgpzp80c.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
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).