Skip to main content

News

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - N E O

556
Engine Development / Re: TurboSphere
New and better sound please, kthxbai! ^_^
557
Spherical News / Re: **READ ME FIRST
I'll take a look at the forums tomorrow and likely choose to restore normal posting then. The wiki is another story entirely, however. :/
558
Site Comments / Re: Spherical Wiki
I'm thinking of disabling normal wiki account creation and instead offloading it to OpenID integration via an extension. Are there any here with any particular objections to OpenID as the wiki account mechanism?
559
Game Development / Re: The Screenshot Thread
@Radnen - you can bookmark line numbers on GitHub by adding #Lx to the URL, where x is the line number without zero-padding.

Also, that stack trace is WAY better than the stack trace method I used to use (same technique, but not nearly as in-depth; I think I was the second one to use it, and I probably copied Tung's or kamatsu's work or something).
560
Engine Development / Re: TurboSphere
Do you use Code::Blocks for non-VS IDE on Windows? I vaguely remember it having some sort of Makefile generation capabilities in it.

Also, now that you have a GitHub account, why not mirror TS source on it?
561
Spherical News / Re: Sphere on GitHub
FlyingJester added to sphere-group app & engine teams :)
562
Added to sphere-doc. Re generating from the wiki, I plan on installing the PDFBook extension once I speak to Dom abt ghostscript and other dependencies so we can theoretically generate a PDF from a collection of articles.
563
Spherical News / Re: **READ ME FIRST
So far not on the forums, but I apparently need to bolster the wiki's security.
564
Right now, the Sphere source distribution is a mishmash of the engine, the editor, and the configurator. I think this was one of the key points preventing new devs from coming in and contributing to any particular aspect of the thing. Radnen's concentration on a new editor and Flying Jester's concentration on re-engineering the engine to use V8 JavaScript instead of SpiderMonkey JavaScript proved that if focus is applied to one aspect of the overarching Sphere project then devs of any decent experience level can come in and contribute something worthwhile that gets finished (or as close to finished as we're going to have).

While there are some interdependent parts between the three apps, I believe the logical move to advance development of the engine, and inevitably the project as a whole, is to split up the source, therefore split the repo into three. Once alpha123's advancement of the base Sphere engine to version 1.7 is complete and gold, such a project separation will be instituted to allow implicit focus on development of a particular portion of Sphere to happen. I'm creating empty repos on https://github.com/sphere-group and anyone who wants to start getting the appropriate code into repos immediately can pull and if not already a member of sphere-group can send a pull request.

Sphere development will be split into the following:


  • Engine
  • Editor
  • Config
  • Tools (eg, tools like the font converter that used to be separate from the editor but then rolled into it)
  • Doc (for format docs, helpfile, API docs, etc)


If you have a GitHub account, let me know if you're interested in being part of any of these development teams!

(retitled to sync w/other "Future of Sphere" posts/articles ~neo)
565
Site Comments / Re: Spherical Wiki
Ok, so the Check User extension to ban IPs works, but doesn't let be enter a range of IPs. Also, I choose to manually delete users once the IP's been banned. I may need to have someone become a wiki moderator ("bureaucrat" is the wiki term for it) to check wiki sign-ups for spam and to ban IPs in case I'm unable to do it at a given time.

Except for a couple, I have most of the anti-spam extensions Wikipedia does installed onto the wiki. There's one that allows plugins, but I haven't gone searching for them yet.
566
Site Comments / Re: Spherical Wiki

Should Functions go into API:Functions with Functions just redirecting to that, then?


Yes.


I'll begin adding in the function pages I salvaged from ye olde wiki. Should function pages have a TOC? Some of the ones I saved do and some don't.

On the topic of the wiki, some anti-spam control may already be in order...check the recent changes to see what I mean.


re TOC - normally I'd recommend a TOC, but most function pages are so light on content that it doesn't really need them. Explicitly __NOTOC__ them from now on, thanks.

re spam - I'm actually going to do that right now. Thanks for the heads up!
567
Site Comments / Re: Spherical Wiki
Wiki procedure update: when writing articles now, please put Sphere API in the namespace API and custom scripts in the namespace Script.

For example, my bezier curve script article is now located at http://wiki.spheredev.org/Script:Bézier_curves but there's a redirect from a namespace-less article because I wanted to.

So, for example, a Sphere function or object article would be called API:CreateColor instead of simply CreateColor; making the namespace-less version redirect is optional, but depending on wiki expansion the namespace-less article may become a disambiguation page instead of a full-on redirect.
568
Libraries / Re: RadLib
How easy would it be to extend it or integrate either someone else's code into this or this into someone else's code?
569
Site Comments / Re: Spherical Wiki

About the wiki, would it be kosher for me to post some TurboSphere pages there?


Do what DaVince suggested first and keep them localized to your user page until it's finalized; after that, I'm all for a TurboSphere wiki namespace (eg, TS-specific articles will be prefixed TurboSphere: with TS: being an alias to the namespace).



...

This sounds good to me, I think. You're saying that functions will be marked both for Sphere and TurboSphere, but only marked with a version for Sphere, and not have a 'version  introduced' tag for TurboSphere, right?

Also, once TS 1.0 (which should be on par with 1.5, or so I'm planning) is released I'll be moving to the X.Y version numbers for TS, too.


I'm saying if something is introduced in TurboSphere, whether it gets backported to vanilla Sphere or not, it should have a category/tag like "Introduced in TS vX.Y" or something but only once TS is on par w/1.5 (let's assume TS 1.0 will be this parity version). Anything TS introduced before 1.0 would say "Introduced in TS v1.0" because we wouldn't count TS introductions before that.

On a related note, I'd recommend that once TS 1.0 is out and 1.5 parity is obtained, the next goal should be 1.6 parity and then a version jump for TS to 1.6 to start matching the appropriate Sphere version from then on.
570
Game Development / Re: The Screenshot Thread
The main advantage of using the built-in map engine over making one of your own is the built-in collision detection when using a Sphere format sprite. If I wasn't so adamant about trying to leverage the built-in offerings of Sphere as much as possible, Artyxx (a shmup) would've been all custom. It still needs work, but at least I didn't have to spend hours writing and testing pixel-perfect collision detection myself (yet; I'll probably have to do it for a web version :/ ).

@Angry_Pirate - great color scheme, very ambient atmosphere! That plus "side-scrolling detective RPG" reminds me a bit of Maniac Mansion...

@Radnen - were you intending on "leaking" Hold the Line 2? ;)