ENIGMA Development Environment

Website is in read-only mode due to a recent attack.

Suggestions are given very low priority. I like the recommended tags idea. Maybe in a large cluster or something like a lot of sites do, with more frequent tags in larger typeset. The template thing only really applies to bugs. A trend seems to be the ability of people in general to propose a solution. Canonical and several others I've observed lately seem to have an answer proposal box at the bottom of each bug report (at least those given attention).

a2h, I'm amazed at how well this all works together. Great job!

Not anymore...? How odd.

I know you can't tell, but I'm smiling right now. Nice work. Now maybe I can get more notice than "Oh, it's too bad ENIGMA segfaults on load..." a month later.

I've asked some British people if they were still sore about it. But yeah, Americans aren't, as a collective, shining jewels of intellect...

Build directory.

Nice change, Ism.

I never liked SDL. Then I found out it had proprietary segments, and now I hate its guts as well as those of all involved with it, in any way. SDL can go fuck itself.

...Still, thanks for the suggestion.

Not while treating it as a plain variable. Allowing operator behavior of -two- types is the difficult part; if it was one or the other, you could use the template magic to make it work, and it would only error if an operator was called that was unsupported. But since, in the case of string and double, only some 8 operators are shared in common, that's problematic.

You could look at boost::variant better than I did. From what I can tell, they scraped something together with accessors. If I were you, I'd recommend overloading operator+(void) and operator-(void) to fetch either type explicitly (Has to be as good as or better than what boost did, but I didn't read very far in).

Our ideals are only slightly off.
"The API would be object-oriented."
By this, I figure you mean Gaming.Engine.Code.Functions.Drawing.Images.SpritesInParticular.Rendering.DrawSprite(
  resources.images.sprites.byIndex(0),
  self.locals.drawing.images.sprite.index,self.locals.position.mouse.x,self.locals.position.mouse.y
);But I'll be damned if I'd put up like that in anything other than Java*. Yes, now that I see your example code, I've noted that you're content with just DrawUtils::DrawRect. But eh, I vastly prefer draw_rectangle, personally.

"BMP, PNG, WAV, OGG and OGV"
I'd not settle for anything not supporting XM. And MP3 is a major plus.

"Contexts: Having many contexts at the same time. Then one'd just apply the functions(begin, end, etc.) to a different context and it'd "just work". OpenGL isn't very context-friendly, since you can only have one active context at any given time."
Easily implemented, major efficiency damper. Each draw function would have to check that the correct context is bound, and the user would have to specify that context every single time. That's annoying to user and GPU.

I don't know what you've used that you're acting as though video is some magically aloof resource that can't be treated as a texture. Must have been one fucked up little library. Happens when libraries do too much for you, I imagine. I can't think of a reason any respectable video renderer wouldn't have FBO's/contexts usable as textures.