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

Re: minisphere

Reply #47 –
NEO: Seems good on the default theme.
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

Reply #48 –
Ok, so the issue is only with my unreleased Spherical theme; I know what needs to be fixed and how, I just wanted to make sure it was only one theme.

Re: minisphere

Reply #50 –
Spectacles runs in minisphere!  There seems to be a good deal of lag on slower machines, though.  Not sure yet if the bottleneck is rendering-related (Allegro) or Duktape though.

Re: minisphere

Reply #51 –
Wow that was fast!
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

Reply #52 –
Yeah, as it turns out the Sphere 1.5 API isn't all that complicated, there's just a LOT of functions.  Most of the graphics APIs would be about 3-5 lines of code if it weren't for all the stack juggling Duktape requires.

So, who's up for trying to compile minisphere on something other than Windows to see how it works? :D

Re: minisphere

Reply #54 –
Quote from: Lord English – on

Yeah, as it turns out the Sphere 1.5 API isn't all that complicated, there's just a LOT of functions.  Most of the graphics APIs would be about 3-5 lines of code if it weren't for all the stack juggling Duktape requires.


Implementing the Sphere graphics API was precisely what lead me to believe that it would be better to have a very small API, even if it were a little more verbose. That's why TurboSphere just has the Shape and Group objects, and no primitives or even direct Surface or Image blitting at all.

Quote from: Lord English – on

So, who's up for trying to compile minisphere on something other than Windows to see how it works? :D


I can give it a try on some other platforms.

I already tried earlier, and I found the following:

Solaris US: Doesn't work, Allegro doesn't work there.
FreeBSD: Same
Haiku: Same

But I assume you are more interested in Linux and OS X.

Re: minisphere

Reply #55 –
Quote from: Flying Jester – on

Quote from: Lord English – on

Yeah, as it turns out the Sphere 1.5 API isn't all that complicated, there's just a LOT of functions.  Most of the graphics APIs would be about 3-5 lines of code if it weren't for all the stack juggling Duktape requires.


Implementing the Sphere graphics API was precisely what lead me to believe that it would be better to have a very small API, even if it were a little more verbose. That's why TurboSphere just has the Shape and Group objects, and no primitives or even direct Surface or Image blitting at all.

Quote from: Lord English – on

So, who's up for trying to compile minisphere on something other than Windows to see how it works? :D


I can give it a try on some other platforms.

I already tried earlier, and I found the following:

Solaris US: Doesn't work, Allegro doesn't work there.
FreeBSD: Same
Haiku: Same

But I assume you are more interested in Linux and OS X.


Yeah, Linux and OS X are my main concerns.  Honestly I don't know anyone that uses Solaris or FreeBSD (although I assume the latter is more common), and I've never even heard of Haiku.

Re: minisphere

Reply #56 –
I keep getting a "syntax error: parse error (line 10)". I've tried to run the startup game or other games, but with no luck.

I'm also surprised that for a minisphere it's the same size on disk as my SSFML. But the memory use should be much, much shallower in yours.
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

Reply #57 –
Quote from: Radnen – on

I keep getting a "syntax error: parse error (line 10)". I've tried to run the startup game or other games, but with no luck.

I'm also surprised that for a minisphere it's the same size on disk as my SSFML. But the memory use should be much, much shallower in yours.


Parse error means it encountered const.  If you change the consts to vars, you'll have a better shot at running it.

Also: It's still smaller than Sphere 1.5.  About half the size at last check.  Also a much smaller codebase.  Vanilla Sphere's codebase is frankly huge for such a simple engine.

Re: minisphere

Reply #58 –
Quote from: Lord English – on

Also: It's still smaller than Sphere 1.5.  About half the size at last check.  Also a much smaller codebase.  Vanilla Sphere's codebase is frankly huge for such a simple engine.


Even if you include all the Allegro libraries? Sphere's codebase includes the entire editor, too (which has some guts in many shared components), as well as the loaders for many audio file types, image types (including all of libungif), and the binaries include the MSVC runtime, as well as several graphics plugins.

I'd be surprised if, including all the necessary libraries, minisphere was actually able to open all the same file types as Sphere, play most of the same games (stuff like const notwithstanding), and was still less than half the size.

Re: minisphere

Reply #59 –
It still says that error no matter how simple of a script I put in it, even if it has <10 lines code.
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