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 21:38:47 +0200
Message-ID: <Zob6R+owyxShGmi0@phare.normalesup.org> (raw)
In-Reply-To: <CAPYw7P4f2a2WUs5oFfyOM4PZ3oUn5ioZ+0zgAP-whTFH8A2nFw@mail.gmail.com>
Paul B Mahol (12024-07-04):
> Application vendor will issue new free-update with handling for newly
> introduced AVOption type.
So you mean your users have tu update your application to have it handle
new types in more recent FFmpeg?
How do they do if you moved to another project and do not update?
What do they do if in the meantime you raised your prices?
My version is superior: I put the unknown options in a text entry
widget, as text, and they work immediately. If later I update the
application, they will work nice, but they already work now.
This is the kind of thing you have to think about when you design an
API.
--
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 19:38 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
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 [this message]
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=Zob6R+owyxShGmi0@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