Nothing is impossible, but by the time you limit it to file://, localhost (or remotely if logged in) and the ability to encode/decode URLs, you will have recreated 90% of busybox's httpd with 20% of the functionality and additional code to maintain.BarryK wrote:Yeah, but there is no way of doing it without running a local web server, is there?technosaurus wrote:Regarding the exec "feature", this can be done more securely using cgi scripts on localhost like slitaz does for a lot of their apps (things we typically use gtkdialog for)
Maybe it is possible to define a custom url protocol, did see something about that for firefox.
About a decade ago I just added additional mime type handlers to SeaMonkey that when clicked, would start a particular app if it ended with a specific file extension...
netsurf could use some work on its internal mime type handling, which is hard coded in C, but its fairly safe/secure. It's JavaScript interface is also relatively new and testing has shown that full support will require a refreshing layout system (libnslayout)
The gtk version of netsurf is probably more tested and suitable for puppy-like systems, but I am interested in the framebuffer version for use in kernels with a fully functioning, built-in initramfs with wayland or X provided as an extension and a gtk3 extension provided by broadwayd. Using netsurf-framebuffer and the slitaz httpd style apps with gtk3+broadwayd for things like libre office, is currently the only way I know to allow a seamless transition between X, framebuffer and wayland (and others) I really don't expect anyone else is interested in it... just an itch I wanted to scratch to get a fully functioning base system back to less than floppy, yet fully and seamlessly extensible regardless of the future desktop; whether it be X, Wayland or something completely different.