From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Sorry state of AVOptions
Date: Thu, 4 Jul 2024 20:34:06 +0200
Message-ID: <ZobrHrNYMzXjo5We@phare.normalesup.org> (raw)
In-Reply-To: <CAPYw7P6HKq7rXz7rTP7M-Y5d8Zm29sixBwKC=WHvTLSCo5BC3A@mail.gmail.com>
Paul B Mahol (12024-07-04):
> Modern humanoids use GUI interfaces and there text interface is reserved
> only for actual text - STRING AVOptions and some aliases for other
> AVOptions types.
GUI can only exist for types that are known by the application or the
GUI toolkit it uses. If you are using a 2026 FFmpeg with an application
from 2024, all the types introduced in FFmpeg between 2024 and 2026 will
be and cannot have a specific GUI, unless they are trivial enumerations.
This is why you need powerful text manipulation even with GUIs.
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-07-04 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 14:44 Paul B Mahol
2024-07-04 14:47 ` James Almer
2024-07-04 14:56 ` Paul B Mahol
2024-07-04 17:03 ` Paul B Mahol
2024-07-04 18:34 ` Nicolas George [this message]
2024-07-04 18:36 ` Paul B Mahol
2024-07-04 19:33 ` Nicolas George
2024-07-04 19:35 ` Paul B Mahol
2024-07-04 19:38 ` Nicolas George
2024-07-04 20:09 ` Paul B Mahol
2024-07-04 20:12 ` Nicolas George
2024-07-04 20:13 ` Paul B Mahol
2024-07-04 15:12 ` Nicolas George
2024-07-05 19:50 ` Michael Niedermayer
2024-07-05 20:09 ` Paul B Mahol
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=ZobrHrNYMzXjo5We@phare.normalesup.org \
--to=george@nsup.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git