Quote from: Eggbert on September 08, 2017, 03:54:55 amThe worst part is that I'll have to come up with a new name, since QtSphere IDE without Qt obviously makes no sense.ElectroSphere? ElectroSphere IDE? That sounds like an IDE for something called ElectroSphere. Sphere Zapper?Any other ideas?Simplistic suggestion: Spheretron?
The worst part is that I'll have to come up with a new name, since QtSphere IDE without Qt obviously makes no sense.ElectroSphere? ElectroSphere IDE? That sounds like an IDE for something called ElectroSphere. Sphere Zapper?Any other ideas?
I would actually like to make a VSCode plugin for Sphere v2. It would support the entire toolchain: miniSphere, Cell and SSj. I have to learn how to make extensions for it first, though.
Quote from: Miscreant on September 08, 2017, 04:06:33 amSimplistic suggestion: Spheretron?IonoSphere (both referencing Ionized air and the Ionosphere itself)StatiSphere (Static + Sphere)BlitSphere/BlitzSphere (Blitz, German for Lightning, + Sphere)
Simplistic suggestion: Spheretron?
Quote from: Chad Zechs on September 08, 2017, 10:52:01 amIonoSphere (both referencing Ionized air and the Ionosphere itself)StatiSphere (Static + Sphere)BlitSphere/BlitzSphere (Blitz, German for Lightning, + Sphere)Hmm, those could work
IonoSphere (both referencing Ionized air and the Ionosphere itself)StatiSphere (Static + Sphere)BlitSphere/BlitzSphere (Blitz, German for Lightning, + Sphere)
let pig = 812;/* .......... */let pig = 1208;
One thing I like about ES6 is that if you do this:Code: (javascript) [Select]let pig = 812;/* .......... */let pig = 1208;You get a runtime error. Also modules are strict mode by default so if you forget to declare a variable that's an error too. It's still indeed nice if the IDE catches it first, though.
Also nice: let is block-scoped, like in C, and the variable is not hoisted so if you use it before the declaration, you *also* get a runtime error. The JS community has given that phenomenon a name: the variable is said to be in the "temporal dead zone". Pretty goofy, huh?
// console.log(y); // strict mode errorconsole.log(x); // undefined (!)var x = 812;console.log(x); // 812
// console.log(x); // error (TDZ)let x = 812;console.log(x); // 812
I can't begin to guess why someone decided to add "Temporal Dead Zone" to our vocabulary, other than that it probably followed a 17-hour binge-watch of ST:TNG accompanied by too much hipster brew.Those of us who have been programming in Java, C++, and the like for the last two decades or so just call those "the place where I haven't yet declared the variable I want to use." I think life would have been better for all concerned if braces defined block scope and we could just be done with it. (Maybe not better for Brendan back in the day, but better now, IMHO.)
var a = true;if(a) { var b = 43; let c = 44;}console.log(b); // 43console.log(c); // error
A key reason I'm sticking with QT Creator at the moment is that it has some useful automatic JS checking for me.
Quote from: Rhuan on September 10, 2017, 09:45:07 amA key reason I'm sticking with QT Creator at the moment is that it has some useful automatic JS checking for me.Honestly, as long as it stays maintainable (unlike the original Sphere engine/editor at a certain point), I'm fine with either idea of it being Qt-based or Electron based. I'd just really like to see a cross-platform editor solution.I do think it'd be more likely for more people to contribute directly to the project if it were coded in HTML/CSS/JS though, even for just tiny additions/fixes. Simply because the barrier of entry is that much lower.