Automatically parse the argument-value entered data

[iG8R]

Hi.
Could you please implement the autoparser for the manually entered arguments?
Currently, when a user wants to add, e.g., --downloader aria2c --downloader m3u8,dash:native -N 8, they are forced to enter it one by one:
--downloader ->
Enter ->
aria2c ->
Enter ->
--downloader ->
Enter ->
m3u8,dash:native ->
Enter ->
-N ->
Enter ->
8 ->
Enter
Phew, what a relief...
It would be much more convenient if the app will parse the entire input itself.

[database64128]

As I mentioned in #183 (comment), I very much prefer the current design. But I suppose we could make this an option, and allow users like you to switch to a shell-like parser for custom arguments.

Welp, more work for me. I'll insist that we keep the current design as the default.

[iG8R]

Thank you very much in advance.
I'd prefer to have a simple input field - it allows conveniently both entering and editing arguments, but right now, e.g., I have the following arguments:

And how could I edit m3u8,dash:native?

[iG8R]

The Download path and Output template input fields are the best example for the Arguments input field.

[iG8R]

Also, it would be great to have tooltip from the yt-dlp help for each argument, after all, the main role of every app is to make the user's life easier, and this would be seen as a time-saving and work-facilitating approach.

[database64128]

I'd prefer to have a simple input field - it allows conveniently both entering and editing arguments

Yeah, makes sense. Let's keep the chips for displaying generated arguments, and add a multi-line text field for custom arguments. What do you think?

The Download path and Output template input fields are the best example for the Arguments input field.

Are you saying you want to also keep a history of used custom arguments?

Also, it would be great to have tooltip from the yt-dlp help for each argument, after all, the main role of every app is to make the user's life easier, and this would be seen as a time-saving and work-facilitating approach.

That just sounds like never-ending work of keeping up with ever-changing upstream documentation. I would say I'm also a user and this definitely won't make my life easier.

Hot take: The goal of a commercial app is to make money. The goal of a small FOSS app like this one is to make the author's life easier.

[iG8R]

Let's keep the chips for displaying generated arguments, and add a multi-line text field for custom arguments.

It would be great:)

Are you saying you want to also keep a history of used custom arguments?

Yes.

That just sounds like never-ending work of keeping up with ever-changing upstream documentation. I would say I'm also a user and this definitely won't make my life easier.

Hot take: The goal of a commercial app is to make money. The goal of a small FOSS app like this one is to make the author's life easier.

Yes, I know, it's a huge part of the work, but if it were a parser that would do this automatically or at least semi-automatically, read the documentation from the yt-dlp repository, find the argument and its description, and place it in a tooltip, that would be so great. But these are just my thoughts out loud. Even without that, your application is excellent :)