Skip to main content ↑ ↓
Topic: neoSphere 5.10.1 (Read 8505681 times) previous topic - next topic
0 Members and 17 Guests are viewing this topic.

Re: miniSphere 5.0rc

Reply #2160 –
Quote from: Fat Cerberus – on
Release is still on track for the 31st so get ready, the best miniSphere release yet is almost here!  8)

Nice! Can't wait. :)
If you use code to help you code you can use less code to code. Also, I have approximate knowledge of many things.

Sphere-sfml here
Sphere Studio editor here

Re: miniSphere 5.0rc

Reply #2161 –
Here's a new time-saving feature coming to SSj 5.0: quick refs.  These give you a way to quickly drill down into objects using the examine command without having to keep retyping property names over and over again.  For example:

Code: [Select]
src/SEngine.mjs:230 [anonymous function]
(ssj) v
var  j        0
var  done     false
var  entity   {...} *42
var  vec      {...} *56
var  target   {...} *70
var  runTime  {...} *84
var  inputs   {...} *98

src/SEngine.mjs:230 [anonymous function]
(ssj) x *84
prop  __proto__    {...} *115
prop  HUD          {...} *116
prop  windowStyle  {...} *117
prop  input        {...} *118
prop  font         {...} *119
prop  x            5
prop  y            320
prop  width        630
prop  height       150
prop  queue        {...} *124
prop  keys         {...} *125

Speaking of time-savers, it's also no longer necessary to quote an expression for eval or examine when it contains spaces, you can just type, e.g., eval 2 + 2 and it will work. :)

Re: miniSphere 5.0rc

Reply #2162 –
I've got more free time now and have started diving into miniSphere. I gotta say, the way you set things up it's actually pretty easy to get started, especially with all the useful core libraries and the debugger! Nice work. :smiley_cat:

Re: miniSphere 5.0.0

Reply #2163 –
Just in time for Halloween :jack_o_lantern:, miniSphere 5.0 final has been released, bringing a scary amount of improvements including long-awaited support for ES2015+ and a blazing-fast JavaScript engine in ChakraCore.  miniSphere 5.0 also brings some brand-new Sphere Runtime modules, many API refinements and freezes the Core API to ensure that code written for Sphere v2 today will continue to work in all future engine versions.*  SSj has also been updated with some time-saving features.

This release includes many, many breaking changes over miniSphere 4.8.x, so be sure to look over the release notes and changelog here:
https://github.com/fatcerberus/minisphere/releases

Be sure to uninstall any previous version of miniSphere, including pre-release versions of 5.0, before setting up 5.0.0.  Many files were removed or renamed, so it's good to start with a clean slate to ensure cruft from previous builds doesn't interfere.

* Note: API freeze applies only to the Core API in miniSphere 5.0; the Sphere Runtime API freeze is currently scheduled for the next major version release (6.0).

Re: miniSphere 5.0.0

Reply #2165 –
There's now a macOS build of 5.0.0 available for download courtesy of @Rhuan.  With that, miniSphere now officially supports all three major desktop platforms.  Hooray! :smile:

Re: miniSphere 5.0.0

Reply #2166 –
Great work!! I'll definitely check this out when I get home!
If you use code to help you code you can use less code to code. Also, I have approximate knowledge of many things.

Sphere-sfml here
Sphere Studio editor here
 

Re: miniSphere 5.0.1

Reply #2173 –
Quote from: Eggbertx – on
I'm not sure if it's something I'm doing wrong, but calling Sphere.restart() seems to cause a massive slowdown

That's a weird one.  I'll definitely look into that!

It could be that closing down CC and reinitializing it disables the JIT somehow, but that level of slowdown shouldn't be noticeable unless you're doing something really intense like mp3 decoding (Chakra's bytecode interpreter is faster than Duktape's).  So it's probably something else.

Re: miniSphere 5.0.1

Reply #2174 –
@Eggbertx Okay, I can reproduce the bug.  Even Specs (which worked fine under Duktape) drops to like 15fps after calling Sphere.restart().  So I don't think it's related to CC at all.  I'll profile the engine to investigate further where the slowdown might be.