From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id B79E94DB49 for ; Fri, 28 Feb 2025 13:52:00 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D777868DBD7; Fri, 28 Feb 2025 15:51:57 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id CC63F68D5D4 for ; Fri, 28 Feb 2025 15:51:50 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 51SDpoKA003687 for ; Fri, 28 Feb 2025 14:51:50 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id 10FDC2EFE4; Fri, 28 Feb 2025 14:51:50 +0100 (CET) Date: Fri, 28 Feb 2025 14:51:50 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Fri, 28 Feb 2025 14:51:50 +0100 (CET) Subject: Re: [FFmpeg-devel] [PATCH v2 0/8] [RFC] avtextformat: Transform text writing into an independent API X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: ffmpegagent (HE12025-02-28): > This patchset doesn't aim to improve or change the API itself - that would > be a bit too much at once. So you asked for advice, got come counsel from me and did exactly the opposite. Do not be surprised if the result is less than satisfactory. > * Public API isn't documented yet When designing a public API, the user documentation, and in particular a quick-start guide with clear examples, should be the first thing you show, and probably even one of the very first things you write. Without that, I can only repeat what I told you two days ago: The writers in ffprobe are an ad-hoc construction to turn the shallow data structures produced by ffprobe into a common denominator of JSON, XML, CSV and a few custom formats. It is not a good candidate to be turned into 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".