From: Juliusz Chroboczek <jch@irif.fr> To: Fabrice Rouillier <fabrice@rouillier.fr> Cc: galene@lists.galene.org Subject: [Galene] Re: Galene & Raspberry Date: Wed, 27 Apr 2022 14:10:23 +0200 [thread overview] Message-ID: <87sfpyk9qo.wl-jch@irif.fr> (raw) In-Reply-To: <E79C83F3-15B5-44F0-A0FF-EECD3897AF27@rouillier.fr> > In particular, compared with the situation with a 32 bit OS and a default configuration for the wireless : > > - the clients connect much more quickly > - the charge of the RPI stays very low (with 4 people connected the > change of each core did stay below 15% while it was more than 50% with > my previous settings) That's interesting -- perhaps I should do some profiling on 32-bit ARM to see where the inefficiency comes from. > In particular, this combo becomes a light and very efficient solution > for a use with the family. Please tell your family that Galene's author said hi ! > - would it be difficult to implement a « ring button » in order that > a new visitor can send a notification to the other people who are > connected but not in front of their Galene Window ? 1. Add the button in galene.html and style it in galene.css. 2. In galene.js, add a callback that sends a broadcast user message: mybutton.onclick = e => { serverConnection.userMessage('ring', nil); }; 3. In onUserMessage, add a handler for the new message: case 'ring': { let audio = new Audio('ring.mp3'); audio.play(); break; } > - would it be difficult tu implement different landing pages, for > example one where we just ask for a pseudo ? You have two solutions. The quick and dirty one would be to edit the div with class "login-container" in galene.html. If you need to supply passwords or change the username, you may do that in the function 'gotConnected' in galene.js. The alternative would be to write your own login server that computes a JWT token and redirects to Galene. The advantage is that you can write the server in any language you wish, but it's a little more complicated. See the section 'Authentication Portal' of the file README.PROTOCOL. -- Juliusz
next prev parent reply other threads:[~2022-04-27 12:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-27 5:01 [Galene] " Fabrice Rouillier 2022-04-27 12:10 ` Juliusz Chroboczek [this message] 2022-04-27 18:37 ` [Galene] " Fabrice Rouillier 2022-04-28 9:56 ` Juliusz Chroboczek 2022-04-28 16:33 ` Fabrice Rouillier 2022-04-28 16:48 ` Juliusz Chroboczek 2022-04-28 17:07 ` Fabrice Rouillier 2022-04-28 16:11 ` Juliusz Chroboczek
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=87sfpyk9qo.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=fabrice@rouillier.fr \ --cc=galene@lists.galene.org \ --subject='[Galene] Re: Galene & Raspberry' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox