Skip to content
This repository has been archived by the owner on Jun 9, 2022. It is now read-only.

displaying a Google Slides doc in a carousel #11

Closed
railsagainstignorance opened this issue Nov 18, 2015 · 9 comments · Fixed by #52
Closed

displaying a Google Slides doc in a carousel #11

railsagainstignorance opened this issue Nov 18, 2015 · 9 comments · Fixed by #52
Assignees

Comments

@railsagainstignorance
Copy link
Contributor

Georgia (et al) would like to be able to
(a) display a google slides doc without any hassles, and
(b) to include one in a carousel

@seanmtracey
Copy link
Contributor

Should be fine in any Electron-powered version of Screens. Can update the carousel so that if it's in Electron, it uses WebViews instead of iframes. Webviews are already implemented for viewing content (such as YT vids and other sites that fall foul of CORs), so it should work.

@AdaRoseCannon
Copy link
Contributor

Electron now uses webviews so this should be possible now, closing this issue.

@JakeChampion
Copy link
Contributor

Electron Screens only uses Webviews for the main iframe. We have yet to create Electron specific carousel and layout systems.

@JakeChampion JakeChampion reopened this Dec 2, 2015
@JakeChampion
Copy link
Contributor

Could we test this out and see if it works?

@AdaRoseCannon
Copy link
Contributor

@seanmtracey please can you quickly test this in an electron build if you get a sec?

@seanmtracey
Copy link
Contributor

I can't confirm that the carousels work in Electron. Unsure as to why atm, but we should hold off merging any logic until we know the cause.

@JakeChampion
Copy link
Contributor

There is no implementation of carousels that works with Electron's webviews instead of iframes. We did a small attempt at this to see if it was possible.

Electron can not house a webview within a webview, this means we can't replace iframes with webviews.

To get carousels working we could follow what the Chrome extension has done, which is to reimplement the viewer page and all functionality which involves iframes. We have not done this as of yet because the demand for such functionality is not high. It is definitely something we should look into however, we would then have 3 implementations of the viewer logic, I'm not sure that is a good thing. We could attempt to create a commonJS/ES6 module which houses most of the logic which the 3 viewers could inherit or extend.

@AdaRoseCannon
Copy link
Contributor

I am actually agreeing with the commonJS module. I almost did when I did it for the extension but it didn't seem necessary when I didn't expect us to support 3 solutions.

Now it seems very necassary.

@AdaRoseCannon
Copy link
Contributor

This will be fixed by #52

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 a pull request may close this issue.

4 participants