Skip to content
This repository has been archived by the owner on Dec 6, 2018. It is now read-only.

Add fullscreen out of Google VRView iframe #212

Merged
merged 4 commits into from
Jul 11, 2017
Merged

Add fullscreen out of Google VRView iframe #212

merged 4 commits into from
Jul 11, 2017

Conversation

rafa8626
Copy link

@rafa8626 rafa8626 commented Jul 6, 2017

@lincolnfrog and @tommytee this is the code of what I was talking about on #178. When I click play it doesn't go fullscreen using WorldRenderer's code. If you can advise me on how to achieve this I'd appreciate it. Thanks

@rafa8626 rafa8626 changed the title Add fullscreen out of Google VRView iframe [NOT READY YET] Add fullscreen out of Google VRView iframe [ON WORK] Jul 6, 2017
@lincolnfrog
Copy link
Contributor

I fixed the bug where it doesn't go to fullscreen (including these changes) here: #219. Please review.

@rafa8626
Copy link
Author

I see: I missed setting the message's SET_FULLSCREEN in the receiver. You stated that there's an issue in this PR still right? The one related to using ESC to get out of the fullscreen. That happens because the control bar is not visible, and since we removed the button from the iframe is expected unless we change CSS styles for the control bar when using fullscreen. I can create the styles for that but it was intended that way.

@lincolnfrog
Copy link
Contributor

It still creates a bug where the icon is wrong when you hit escape. Do you still want to try to merge this into master? I am of the opinion that this change is fairly custom and most users of vrview will be happy with the default fullscreen behavior. Thoughts?

@rafa8626
Copy link
Author

Could be. I just picture the scenario when you need to use GoogleVRView with any other existing major player and you need to adapt now code to make it work. If we had this PR it could facilitate integration with them. Just my 2 cents

@lincolnfrog
Copy link
Contributor

I am not opposed to merging this PR if we can iron out the details better. In my view, here are the things I would like to see:

  1. add my fix for the SET_FULLSCREEN case statement in the message handler
  2. Fix the bug where when you hit escape the icon doesn't change back to "expand" state
  3. Figure out a way to make the original default fullscreen behavior be the default and allow people to opt-in to this custom handling control paradigm.

If you can meet those three items, I would be interested in merging this.

@rafa8626
Copy link
Author

Sounds good. I'll work on these fixes and I'll give you an update soon. The point 3 is gonna take me some time but I see the value on that. Right now if you just use hideButton as false it will make the fullscreen and VR buttons appear, and that's the original behavior. You need something else on that?

@lincolnfrog
Copy link
Contributor

I think the best thing would be to have your new button not appear by default and the original embedded fullscreen button be the only thing. You can add a section to the README.md about how to enable the custom fullscreen UI and disable the embedded UI. Does that make sense?

@rafa8626
Copy link
Author

Sounds good to me. As long as I can state that is possible to hide the fullscreen button and have a custom one I'm OK with this. So I'll take care of 1 and 2, and add a note on README for 3. Is that ok?

@lincolnfrog
Copy link
Contributor

lincolnfrog commented Jul 10, 2017 via email

@rafa8626
Copy link
Author

In the example I deactivated the fullscreen so I just need to remove that piece of code to be the default functionality. Is that what you meant?

@lincolnfrog
Copy link
Contributor

lincolnfrog commented Jul 10, 2017 via email

@rafa8626
Copy link
Author

OK I'll work on this and I'll let you know when it's ready to review once more. Thanks for your help

@rafa8626
Copy link
Author

OK @lincolnfrog the changes we discussed yesterday are now in place; let me know if you need anything else. Thanks

@@ -4,6 +4,28 @@ VR View allows you to embed 360 degree VR media into websites on desktop and
mobile. For more information, please read the documentation available at
<http://developers.google.com/cardboard/vrview>.

# Configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

This is great!

Copy link
Contributor

@lincolnfrog lincolnfrog left a comment

Choose a reason for hiding this comment

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

This is great! Minor change - please make the param for disabling fullscreen button more descriptive. Happy to merge this after. Thanks for creating that great table of params to the readme!

README.md Outdated
`default_yaw` | Number | (Optional) Numeric angle in degrees of the initial heading for the 360° content. By default, the camera points at the center of the underlying image.
`is_yaw_only` | Boolean | (Optional) When true, prevents roll and pitch. This is intended for stereo panoramas.
`loop` | Boolean | (Optional) When false, stops the loop in the video
`hide_button` | Boolean | (Optional) When true, the fullscreen on video are hidden. Useful when user requires to implement his own fullscreen button
Copy link
Contributor

Choose a reason for hiding this comment

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

this is an overly-generic name. hide_fullscreen_button?

@rafa8626
Copy link
Author

Ok I'll change the name of the configuration and I'll try to come up with a better language for it in the table. I'll get this done in a little

@rafa8626
Copy link
Author

OK changes in place. Let me know your thoughts. Thanks for the feedback

@rafa8626 rafa8626 changed the title Add fullscreen out of Google VRView iframe [ON WORK] Add fullscreen out of Google VRView iframe Jul 11, 2017
@lincolnfrog lincolnfrog merged commit 4e8e57e into googlearchive:master Jul 11, 2017
@rafa8626
Copy link
Author

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants