Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Base "PublicShareAuth" on "Embedded" instead of on "Application" #1633

Merged

Conversation

danxuliu
Copy link
Member

This is just a refactoring, so everything should work in the public share authentication page as before.

danxuliu added 5 commits March 5, 2019 13:59
For legacy reasons the "incall" CSS class, which is used to hide and
show the empty content view and the call container as needed, and the
"screensharing" CSS class, which is used to adjust the call UI when
there are shared screens, were set in the "#talk-sidebar" element of
PublicShareAuth. For consistency with the embedded Talk UI now the
classes are set in the "#call-container" instead.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This is just a copy of the App code related to guest names; both codes
should be refactored and extracted to a common place, but for now
copying it is good enough.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
"Embedded" does not provide a method to change the page title, as in
general only full apps should do that. However, in the case of the Talk
UI in the public share authentication page it makes sense to change the
page title; once PublicShareAuth is based on Embedded instead of on
Application it will no longer have access to that method, so now
PublicShareAuth uses its own copy.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
hen PublicShareAuth was introduced there was no Embedded class, so it
had to be based on Application. However, Application should be used only
for the main Talk UI and, as its name implies, Embedded should be used
for any embedded Talk UI.

Some minor adjustments are needed to PublicShareAuth due to the
differences between Application and Embedded: unlike in Application, the
empty content view is not created by Embedded, so there is no need to
destroy it; Embedded does not render the local video view by default, so
it needs to be explicitly rendered; there is no fullscreen button for
embedded apps, so there is no need to register its handler; and finally,
the chat view needs to be explicitly detached when the room is left, as
Embedded does not handle UI states.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Now that PublicShareAuth is based in Embedded there is no need to
explicitly show the videos and screens when the sidebar is open again,
as they will not have been hidden.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@danxuliu danxuliu added 3. to review feature: talk-sidebar ⬅️ Sidebar integration of Talk into other apps like sharing and documents labels Mar 15, 2019
@danxuliu danxuliu added this to the 💚 Next Major milestone Mar 15, 2019
Copy link
Member

@Ivansss Ivansss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything seems to work as before

@Ivansss Ivansss merged commit 8b4708a into master Mar 19, 2019
@Ivansss Ivansss deleted the base-publicshareauth-on-embedded-instead-of-on-application branch March 19, 2019 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review feature: talk-sidebar ⬅️ Sidebar integration of Talk into other apps like sharing and documents
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants