Hi Didier,
Web APIs have advanced since you last checked. The Service Worker (
https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) can
keep running in background your briowser after the web page has closed.
The Notification API (
https://developer.mozilla.org/en-US/docs/Web/API/Notification) can display
local system notifications from the Service Worker. It is also possible to
access a web page through its normal URL when the system is actually
disconnected from the network, and for the page to work offline (
https://developer.mozilla.org/en-US/docs/Web/API/Cache).
Thanks
Bruce
On Mon, Dec 30, 2024 at 3:28 AM Didier Kryn <kryn@???> wrote:
> Le 30/12/2024 à 03:26, Bruce Perens via Dng a écrit :
> > These days, it makes sense for everything I write to have a web
> > interface. Most of our compiled and interpretive languages run
> > everywhere as long as you don't start working with the native GUI, and
> > there's no need to port a web-based GUI. There aren't any facilities
> > that we would expect on a native GUI and are missing from the web
> > these days.
>
> That's obviously true for applications running on a host which is
> remote to the user. And, of course, such applications can be reached
> through localhost. A good example is the Cups interface on port 631. I
> have some home-made applications also (~:
>
> However there are simple things which cannot work like this, for
> example an application which remains sleeping and hidden and just pops
> up an interactive window when some event happens. Also one needs to
> reserve one port for every such web server and keep them in the
> browser's bookmark.
>
> -- Didier
>
> _______________________________________________
> Dng mailing list
> Dng@???
> Manage your subscription:
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> Archive: https://lists.dyne.org/lurker/list/dng.en.html
>
--
Bruce Perens K6BP