[Galene] Re: Pyrite update

[Jeroen van Veen <jvanveen@protonmail.com>]

Thanks for the detailed info, this one is on the top of my list to fix.
I still have to fix anonymous login too. Somewhat out-of-scope for now, but I also
would like to see a way where a user can reuse it's session and doesn't have
to go through the login screen every time. I'll probably try to combine that with
the new authorization method that Galene offers.

Jeroen

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Op maandag 24 januari 2022 om 7:49 PM schreef Juliusz Chroboczek <jch@irif.fr>:

> > The login messages are still a bit off, when a login error occurs.
>
> You should make sure that you don't attempt to join before the onconnected
>
> callback has triggered. When the user clicks the join button, you should
>
> render it inactive (grayed out, or whatever), and invoke the
>
> ServerConnection.join method.
>
> In the onjoined callback, you check the "kind" field. If it is "joined",
>
> you update your user interface to the connected state, and send
>
> a "request" message to receive streams (use the "permissions" field to
>
> decide whether to enable the present button). If, on the other hand, kind
>
> is "fail", then you display a suitable error message and go back to the
>
> initial setup.
>
> (Afterwards, you keep listening on the onjoined callback -- kind "change"
>
> indicates that your permissions have changed, which might require you to
>
> update your UI. Kind "leave" indicates that you've left the group, for
>
> example because the administrator has kicked you out.)
>
> -- Juliusz
>
> Galene mailing list -- galene@lists.galene.org
>
> To unsubscribe send an email to galene-leave@lists.galene.org