From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 7/8] fftools/ffmpeg_demux: implement -bsf for input Date: Mon, 22 Jan 2024 09:57:27 +0100 Message-ID: <170591384739.8914.1768446965607573773@lain.khirnov.net> (raw) In-Reply-To: <Za1tYtnLsLM6tbR6@mariano> Quoting Stefano Sabatini (2024-01-21 20:15:46) > On date Sunday 2024-01-21 19:35:01 +0100, Anton Khirnov wrote: > > Quoting Stefano Sabatini (2024-01-21 19:22:35) > > > On date Sunday 2024-01-21 18:43:36 +0100, Anton Khirnov wrote: > > > > Quoting Stefano Sabatini (2024-01-20 12:32:42) > > > [...] > > > > > When you present an example you usually start with an explanation > > > > > (what it does) and then present the command, not the other way around. > > > > > > > > I don't, neither does most literature I can recall. Typically you first > > > > present a thing, then explain its structure. Explaning the structure of > > > > something the reader has not seen yet is backwards, unnatural, and hard > > > > to understand. > > > > > > I still don't understand what "literature" you are referring to. > > > > Various manuals and textbooks I've read. > > > > > If you see most examples in the FFmpeg docs they are in the form: > > > > > Our documentation is widely considered to be somewhere between atrocious > > and unusable > > nah, it's not so bad, also this applies to most documentation > > Besides FFmpeg is possibly the most sophisticated existing toolkit in > terms of features/configuration, so this is somehow expected (at least > if you expect a tutorial rather than a reference). I wouldn't be so sure. E.g. Qt has a bigger and more complex API than ours, yet its documentation is more complete and coherent. > > (and sometimes actively misleading), so the fact that it > > does something in a specific way does not at all mean that it's a good > > idea. > > So what do you propose instead? The fact that it is not perfect does > not mean that everything is bad. I'm not saying everything is bad. I'm saying this specific way of writing examples is bad and should be changed. Which is what I'm doing in this patch. -- Anton Khirnov _______________________________________________ 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-01-22 8:57 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-05 16:42 [FFmpeg-devel] [PATCH 1/8] fftools/ffmpeg_demux: replace abort() by av_assert0(0) Anton Khirnov 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 2/8] doc/ffmpeg: drop documentation for non-existent -sbsf Anton Khirnov 2024-01-06 11:22 ` Stefano Sabatini 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 3/8] fftools/ffmpeg_demux: do not set bitexact directly on the decoder Anton Khirnov 2024-01-06 11:24 ` Stefano Sabatini 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 4/8] fftools/ffmpeg_demux: set options on codec parameters rather than decoder Anton Khirnov 2024-01-06 11:31 ` Stefano Sabatini 2024-01-06 14:22 ` James Almer 2024-01-16 19:49 ` Anton Khirnov 2024-01-16 22:37 ` James Almer 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 5/8] fftools/ffmpeg_demux: only allocate the decoder when actually decoding Anton Khirnov 2024-01-06 11:34 ` Stefano Sabatini 2024-01-16 19:50 ` Anton Khirnov 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 6/8] fftools/ffmpeg_demux: add demuxing thread private data Anton Khirnov 2024-01-06 11:44 ` Stefano Sabatini 2024-01-16 19:52 ` Anton Khirnov 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 7/8] fftools/ffmpeg_demux: implement -bsf for input Anton Khirnov 2024-01-06 12:12 ` Stefano Sabatini 2024-01-17 9:02 ` Anton Khirnov 2024-01-20 11:32 ` Stefano Sabatini 2024-01-21 17:43 ` Anton Khirnov 2024-01-21 18:22 ` Stefano Sabatini 2024-01-21 18:35 ` Anton Khirnov 2024-01-21 19:15 ` Stefano Sabatini 2024-01-22 8:57 ` Anton Khirnov [this message] 2024-01-05 16:42 ` [FFmpeg-devel] [PATCH 8/8] fftools/ffmpeg_opt: mark -stream_group as expert option Anton Khirnov 2024-01-06 12:12 ` Stefano Sabatini 2024-01-06 11:18 ` [FFmpeg-devel] [PATCH 1/8] fftools/ffmpeg_demux: replace abort() by av_assert0(0) Stefano Sabatini
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=170591384739.8914.1768446965607573773@lain.khirnov.net \ --to=anton@khirnov.net \ --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