haikuwebkit: gopher unsupported

[nephele]

Trying to load a gopher:// site will now display "Unsupported protocol"

Probably this happened because of the change to curl?

[pulkomandy]

curl itself supports it, but possibly the curl code in WebKit doesn't allow it. And also, WebKit won't know what to do with the contents anyway, with the native Haiku backend it was the backend doing the work of converting Gopher pages to HTML. This is similar to how we handle FTP and local directories rendering, so it could be done on WebKit side, but probably not something we can upstream.

[nephele]

We likely want a gopher-> html and gemdoc->html translator anyway to use for netservices2 later on, so will keep this in mind.

[pulkomandy]

We should think about something like AmigaOS' MultiView: a tool that can display anything as long as there is a datatype (translator, in BeOS language) for it. They do images, sound, videos, hypertext documents, ... all in the same app.

Web browsers are kind of this with network connectivity and Javascript added on top.

Not sure if that's all a good idea or not... maybe dedicated apps for each thing are better.

[nephele]

In the "each app on its own" case we could likely make a gopher and or gemini client on it's own based on libnetservices2, and not have this in haikuwebkit at all.

I don't think haikuwebkit is a good universal viewer :)

[nephele]

I would be fine with leaving this in netservices1 and not producing a replacement for webpositive, but rather build a native application for gopher or gemini.

Thoughts?

[pulkomandy]

Sounds fine. mmu_man has a branch of NetSurf with Gopher support, I think (probably not up to date with current NetSurf). So that may be an option as well.