Instead of an ever-increasing list of undocumented environment variables like THEBE_DIR it would be nice to get that kind of runtime data from a configuration file...
On Thursday, December 29, 2016 at 11:15:20 AM UTC+1, Erik Bray wrote: > > On Tue, Dec 27, 2016 at 11:34 PM, Paul Masson <paulm...@comcast.net > <javascript:>> wrote: > > I'm very much in favor of making Three.js a standard package, with the > > following caveats: > > > > 1) As of r80 the Three.js library has been reorganized to use ES6 > Modules. > > There is little point in asking people to download the entire library > (even > > with examples excluded as in the current optional package) unless we're > > going to make Node.js a standard package as well. > > > > 2) The template only needs two files to function: the main build file, > > minified or not, and OrbitControls.js for allowing user interaction. As > a > > standard package I'm in favor of Three.js only including the parts of > the > > library that will actually be used. If another file is needed in the > future, > > it can be added then. > > > > 3) As part of the review process of #12402, Andrey asked me explicitly > about > > the ease of embedding Three.js output in web pages. While I certainly > want > > to add a local copy of the required Three.js files for offline use, I'd > like > > to keep the output as portable as possible, and the simplest way to > achieve > > that is with a CDN link in the file. The template can be modified to > check > > for a local copy and fall back to the CDN or vice versa, but the HTTPS > issue > > would still need to be fixed on the server. > > Alternately, a flag can be added to the viewer to specify that > generated > > output will be for online use and the template modified at runtime to > use > > the CDN rather than the local copy. That would of course require an > extra > > input from the end user, but may be preferable to the majority. > > Please see also my recent ticket related to this: > https://trac.sagemath.org/ticket/22061 > > I don't think it's in any way in conflict with this, just something to > keep in mind. > > > On Monday, December 26, 2016 at 7:16:55 PM UTC-8, Andrey Novoseltsev > wrote: > >> > >> Hello, > >> > >> How about making threejs a standard package? > >> > >> It was optional for a while, used in SageMathCell to power its own > version > >> of threejs viewer. https://trac.sagemath.org/ticket/12402 has added > threejs > >> as possible output for a bunch of backends and ideally it will become > >> standard for all interfaces. One of the problems now - the template > loads > >> scripts from the Internet, which means no offline use and causes issues > with > >> HTTPS anyway. > >> > >> Thank you, > >> Andrey > > > > -- > > 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+...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > -- 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.
