On Sunday, January 1, 2017 at 6:18:24 PM UTC-8, Paul Masson wrote: > > On Sunday, January 1, 2017 at 5:33:31 PM UTC-8, Andrey Novoseltsev wrote: >> >> Trying to get back to threejs: >> >> - it is apparently possible to use HTTPS for rawgit.com and it has a CDN >> which we actually must use to avoid being blocked >> > > Sorry for some confusion I've created: I was sure I had used HTTPS in the > template but clearly did not, so that can be changed. Perhaps a better way > is to omit HTTP/HTTPS completely, i.e. a protocol relative URL, when > generating scenes for online use. Would that cause problems from your > perspective? >
Scratch the protocol-relative URL idea. I'll just use HTTPS instead. > > >> - "more usual CDNs" provide threejs, but not extra files like OrbitControl >> - it seems that the recommended way of using threejs is to download and >> serve your own copy >> >> So to me "the right way" seems to be: >> >> - have threejs package in Sage as originally proposed, stripping as much >> as we want (I guess it is perfectly fine to keep just the minified version >> and OrbitControl, adding more stuff later on if it becomes necessary) >> - create scenes that can be downloaded/embedded without any explicit code >> loading threejs >> > - have clear instructions in documentation that one needs to load it and >> have an example, e.g. with https://cdn.rawgit.com >> > > I would rather not generate scenes with no JS source whatsoever, since the > scene wouldn't render at all and the output would look damaged. As I said > above, a protocol relative URL to rawgit.com should solve the problem. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
