From: Zhanbang He <hezhanbang@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Embedded documentation?
Date: Mon, 8 May 2023 23:48:01 +0800
Message-ID: <CALZOGtT-GbfYjJwkSHsgg=z0Co8kMHBqayDuJUgqxcT3HZStsw@mail.gmail.com> (raw)
In-Reply-To: <ZFkYgMxVN9MD4xD1@phare.normalesup.org>
Can it supports chatGPT?
On Monday, May 8, 2023, Nicolas George <george@nsup.org> wrote:
> Stefano Sabatini (12023-05-08):
> > I cannot parse this, where is the threshold value defined?
>
> The threshold is the enum constant that was being described.
>
> > Maybe an example would clarify this, since there is ambiguity about
> > what default and explanations are.
>
> Let us think how this is meant to be used. For example, the user of a
> GUI clicks on a filter, the application asks the library “give me the
> documentation for this” and displays it somewhere.
>
> Imagine the whole FFmpeg documentation as a gigantic hypertext document,
> like <https://ffmpeg.org/ffmpeg-all.html>. Imagine we want the
> documentation for the scale filter. So we start at
> <https://ffmpeg.org/ffmpeg-all.html#scale-1>, and we take:
>
> - the introduction of the scale filter,
> - the width option,
> - the height option,
> - the flags option,
> - the size option,
> - etc.,
> - the examples,
> - the commands,
>
> But the width and height options are expressions, therefore we will need
> also <https://ffmpeg.org/ffmpeg-all.html#Expression-Evaluation>.
> And the size option is a video size, so we take
> <https://ffmpeg.org/ffmpeg-all.html#Video-size> too.
> And the flags option requires
> <https://ffmpeg.org/ffmpeg-all.html#Scaler-Options>.
> And maybe the various scaler flags link to explanations about their pros
> and cons, and we want these explanations too.
>
> In general, to get the documentation for a component, avdoc starts at
> the doc node of this component, and it follows all the links from there,
> and then all the links from the nodes reached, etc., recursively, until
> avdoc has all the documentation that might be useful to understand that
> component. Then it returns to the application.
>
> But that means we will get 50 pages of documentation for most
> components. It is fine to display in a full-fledged help browser, but a
> 50 pages tooltip is not very convenient.
>
> This is where the thresholds come into play:
>
> - if you want a tooltip, av_documentation_get_excerpt(obj, 0);
>
> - if you want a help dialog where scrolling is possible,
> av_documentation_get_excerpt(obj, AVDOC_LINK_SELF_CONTAINED);
>
> - if you want a help browser where hyperlinks are possible,
> av_documentation_get_excerpt(obj, AVDOC_LINK_SELF_CONTAINED_FULL).
>
> Regards,
>
> --
> 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:[~2023-05-08 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 10:13 Nicolas George
2023-05-01 11:28 ` Diederick C. Niehorster
2023-05-03 17:52 ` Nicolas George
2023-05-01 13:15 ` Timo Rothenpieler
2023-05-03 18:01 ` Nicolas George
2023-05-03 19:31 ` Thilo Borgmann
2023-05-07 22:10 ` Stefano Sabatini
2023-05-08 15:03 ` Nicolas George
2023-05-08 15:42 ` Nicolas George
2023-05-08 15:48 ` Zhanbang He [this message]
2023-05-08 16:42 ` Nicolas George
2023-05-08 19:05 ` Nicolas George
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='CALZOGtT-GbfYjJwkSHsgg=z0Co8kMHBqayDuJUgqxcT3HZStsw@mail.gmail.com' \
--to=hezhanbang@gmail.com \
--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