Skip to main content
↑
↓
Spherical forums
Community for the
Sphere game engine
New?
Contact Us
to register an account!
1 Hour
1 Day
1 Week
1 Month
Forever
Community
Help
Search
Recent Posts
Log in
Contact Us
News
Spherical
Facebook
-
Twitter
-
Discord chat
New?
Contact us
to register an account!
Sphere Development
Engine Development
Sphere 2.0: Tonight, We Ride! (into the pig)
1
Print
Topic: Sphere 2.0: Tonight, We Ride! (into the pig)
(Read 4706 times)
previous topic
-
next topic
0 Members and 1 Guest are viewing this topic.
Fat Cerberus
Big Chungus
Posts: 2,774
*MUNCH*
Logged
Global Moderator
Sphere Developer
Sphere 2.0: Tonight, We Ride! (into the pig)
May 03, 2016, 04:51:16 pm
*MUNCH*
This is a placeholder topic for the eventual Sphere 2.0. I've decided to maintain minisphere for a while longer as a backward-compatible engine, and have forked the project for the purposes of the 2.0 overhaul. The GitHub repository is here:
https://github.com/fatcerberus/sphere
edit:
Removed Sphere 2.0 repository for now (I still have the code saved locally), need to get minisphere 3.1 work out of the way first so that the new engine can be based on that instead of 3.0.8. Too many merge conflicts to deal with trying to keep the two engines in sync right now.
Last Edit
: May 06, 2016, 03:02:07 am by Lord English
neoSphere 5.9.2
-
neoSphere
engine -
Cell
compiler -
SSj
debugger
forum thread
|
on GitHub
DaVince
Legendary Poster
Posts: 1,001
Logged
Administrator
Used Sphere for, like, half my life
Re: Sphere 2.0: Tonight, We Ride! (into the pig)
Reply #1
–
May 03, 2016, 05:01:27 pm
Hey, good thinking! Making a clean cut like this might actually be for the best, considering how much the API will be changing.
Spherical Downloads Repo
||
My (really old) Sphere stuff
Fat Cerberus
Big Chungus
Posts: 2,774
*MUNCH*
Logged
Global Moderator
Sphere Developer
Re: Sphere 2.0: Tonight, We Ride! (into the pig)
Reply #2
–
May 03, 2016, 09:13:14 pm
Despite the fork, I'm going to keep the version numbering as-is, to reflect the project's history. As such it will be versioned at v4.0. I still consider this largely experimental--depending on how everything turns out in the end, I may just merge the changes back into the minisphere repo. If I could manage to support both the Vanilla and Pegasus APIs in one engine that'd be awesome too, but one thing at a time.
neoSphere 5.9.2
-
neoSphere
engine -
Cell
compiler -
SSj
debugger
forum thread
|
on GitHub
Fat Cerberus
Big Chungus
Posts: 2,774
*MUNCH*
Logged
Global Moderator
Sphere Developer
Re: Sphere 2.0: Tonight, We Ride! (into the pig)
Reply #3
–
June 11, 2016, 03:08:19 am
So yeah, I decided to ditch the fork and just continue versioning minisphere as normal. We can just say that "Sphere" is the name of the standard and minisphere is the official reference implementation. Sort of like how "Python" is the programming language but the reference implementation is actually called "CPython"
Come to think of it, that was the original idea for minisphere, I believe--to be a reference implementation for the next version of Sphere. It's only taken me 4 versions to finally get there...
)
neoSphere 5.9.2
-
neoSphere
engine -
Cell
compiler -
SSj
debugger
forum thread
|
on GitHub
1
Print
Sphere Development
Engine Development
Sphere 2.0: Tonight, We Ride! (into the pig)