I think the most ellegant solution would be to develop a download
manager and establish a small, pipe-driven protocol to expose download
handling. This way, you can choose to use the suckless download
manager, or make your own shell script, or even use none at all (which
is what would work for our kiosk software).
Think for example the way whiptail --gauge progress bars work;
something like that, but with a few more message types.
https://linux.die.net/man/1/whiptail
On Fri, Mar 23, 2018 at 5:54 AM, Nick <suckless-dev_AT_njw.me.uk> wrote:
> Quoth v4hn:
>> On Thu, Mar 22, 2018 at 08:54:34PM +0000, Nick wrote:
>> > I wonder whether it would be best to move to webkit handling
>> > downloads itself, like this, albeit with a basic user interface.
>>
>> This is not a new thought.
>> Five years ago people thought it a bad idea.
>>
>> https://lists.suckless.org/dev/1301/14371.html
>
> Yeah, I remember that, vaguely. But times have changed. Like
> Quentin, I have definitely found times that surf downloads have
> failed through curl, while they work in alternative browsers. surf
> will always have more suck than we'd like, because of the
> architecture of the web. May as well at least have it handle as much
> as possible of that web correctly.
>
Received on Fri Mar 23 2018 - 17:09:45 CET