Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Help with ES6 modules
Date: Sat, 16 Nov 2024 22:55:24 +0100	[thread overview]
Message-ID: <87o72eq1wz.wl-jch@irif.fr> (raw)

Hi,

I've just started working on background blur in Galene's default client.
I'm using Google selfie segmentation library, which is available as an ES6
module.  That's not a problem, since I'm planning to load it in a web
worker, so that the mail galene.js code does not need to become a module.

Still -- should I migrate the whole of the JS code in Galene to ES6
modules?  In particular, would it inconvenience people if protocol.js
became an ES6 module?  It is my (perhaps erroneous) understanding that
dynamic import is available in non-module code, so that the library will
continue to be usable, but is there anything I'm overlooking?

Thanks,

-- Juliusz


                 reply	other threads:[~2024-11-16 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o72eq1wz.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox