Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 26 Oct 2005
Offline Last Active Aug 02 2013 05:55 PM

Posts I've Made

In Topic: OtterUI - Open Source UI Library

08 May 2013 - 11:25 AM

Yup - it's included in the repository, as part of the "SampleApp" project.  It demos not just the different controls, but also what a basic integration would look like.  Also, there's a plugin architecture in place that lets you define and build your controls, as well as the ability to animate them.

In Topic: Where are all the good GUI libraries?

14 April 2013 - 04:49 PM

Hi folks,


I'm the creator of OtterUI.  Thanks for pointing out the old-ass Word doc file - that's a remnant from a time gone by ;)   I've cleaned things up a tad more.  Let me know if you run into anything else.  And, of course, feel free to reach out if you have any questions.


Also, l0cal05t is correct - OtterUI does not provide its own built-in renderer.  I provide a rudimentary one just as a starting point, but after that it's up to you integrate it into your pipeline.  That's done on purpose - I got tired of UI libraries competing against my renderers for whatever reason.  Same goes for File IO, audio, and so on.



In Topic: visual c++ version runs differently than the exe in explorer!

11 April 2013 - 09:54 AM

Debug builds automatically initialize (or zero out) your variables for you, while Release builds retain whatever garbage value is presently set at that location in memory your variables refer to.


Whenever you create a new map entity object, set flags = 0 in the constructor.  That should do it.

In Topic: Is C++ too complex?

05 December 2012 - 05:57 PM

That question makes no sense to me.

The problem is that no first-year CS course will cover all the things you have to know to use C++ proficiently. It's like asking "what's so hard about being a chef? Limit your answers to the subject of boiling water."

Well, yeah, boiling water isn't hard. There's a lot more to being a chef than boiling water.

OK, that's fair, but the point is that the stuff I deal with regularly with regards to C++ I, personally, do not find very hard nor complex. Instead of 1st year students, let's expand to what one might learn throughout your 4-year degree. Or maybe in your first year being a software engineer. A lot of things that are considered "too complex" I very rarely encounter, and that's clear across 14 years of dedicated C++ development. Moreover, what I'm particularly interested in is what makes C++ more complex than Java (or C#), at the beginner/novice level, without going into language obscurities that most people may not deal with.

In Topic: Is C++ too complex?

03 December 2012 - 08:23 PM

Ok, reading through the comments, and the general "it's too complex, not a walk in the park, long time for something shiny on the screen, etc" hand-wavy consensus - I'm really curious: What, specifically, from the folks that consider the language overly complex, are the overly complex pieces of the language?

And I'm not talking about relatively obscure tricks/"abuses" of the languages. I'm talking about stuff you'll learn in your first years of Comp Sci, or an intro-to-C++ book.

I mean, I've seen my fair share of heinous code. In all manner of languages: C, C++, Java, C#, Python, LUA .. you name it. But what makes it complex has never been the language as much as the complexity of the code. In other words, I rarely ask myself: "Damn, what does this language feature do?" but rather ask "why in the world has the developer done this?"

I do believe, though, that pointers and the usage thereof continually trip folks up with regard to C *and* C++, and with good reason. Pointer management takes a while to get a good grasp of, but even Pascal had pointers and I can count on my left foot the number of times someone has said "Pascal is too complex" :) Even though Java and C# have *many* more language features than C and C++ combined, the fact that they (mostly) completely hide pointers and memory management makes it easier for most programmers to write code and not worry about memory consequences, right off the bat.

So, again, what *exactly* makes C++ so complex over, say, Java? Pointers aside, and considering only what you may learn in your first year as a CS student? (I make that distinction because as you spend more time in any language you'll eventually learn all sorts of 'interesting' things that'll make most folks' heads spin)