Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Control Flow

2 (2.2%)

Arrays, Strings, Pointers, and References

8 (9%)

Functions

4 (4.5%)

Basic object-oriented programming

30 (33.7%)

A bit more advanced OOP (Composition, Operator overloading, Inheritance, Virtual Functions)

18 (20.2%)

Templates

8 (9%)

Other (Explain)

4 (4.5%)

Working with files?  (Streams)

15 (16.9%)

Total Members Voted: 89

[TolyK]

sfml - ?

[Siquo]

SFML

But it's a matter of taste and purpose, mostly. SDL has more options, better sprite engine, etc, but SFML is more lightweight and more OO than SDL.

[TolyK]

SFML

But it's a matter of taste and purpose, mostly. SDL has more options, better sprite engine, etc, but SFML is more lightweight and more OO than SDL.

hmm... thanks for giving me more to learn XD
I'll try it out...

[Siquo]

Oh, and a definite plus for the real learner: SDL has numerous tutorials, SFML does not even have complete documentation

[TolyK]

yeah I know, sdl first.
though I've gotten the basic API, I still can't make anything useful 
also: can either of them be implemented as part of another GUI?

[Siquo]

Not sure, have no experience with GUI's in OpenGL yet, but I believe I read somewhere that OpenGL does not like sharing space. So any GUI stuff should be done using OpenGL...

So I looked for a library or something, then found a blogpost on the OpenGL forums of some guy who wanted one as well, and got the advice to write his own. I'm not too sure about that, yet.

[TolyK]

how about visual basic .net?
well sfml says it works with it, sdl will probably too...

also will OpenGL be "embeddable" into a windows form in VB?

[Nadaka]

Hmm. I'm eventually going to have to deal with openGL as well once I get to the point where I actually start thinking about turning my simulations into games. Java supposedly has some decent OpenGL libraries, but I don't know anyone that uses them.

[Mondark]

Java supposedly has some decent OpenGL libraries, but I don't know anyone that uses them.

Now you do.

JOGL is a pretty straightforward set of bindings, if you already know OpenGL you can probably jump right in.  If you just want to make 3D games/simulations in Java, you might be better off looking at LWJGL, a slightly nicer wrapper for JOGL, or JME3, a really very nice toolkit geared towards making games, and it comes complete with easy Bullet physics integration and some nice GUI tools as well.

[SolarShado]

LWJGL

*coughminecraftcough*

[Blank Expression]

Java supposedly has some decent OpenGL libraries, but I don't know anyone that uses them.

Now you do.

JOGL is a pretty straightforward set of bindings, if you already know OpenGL you can probably jump right in.  If you just want to make 3D games/simulations in Java, you might be better off looking at LWJGL, a slightly nicer wrapper for JOGL, or JME3, a really very nice toolkit geared towards making games, and it comes complete with easy Bullet physics integration and some nice GUI tools as well.

JME3 is probably the best way to go in Java. It's not perfect, but the problems are more with Java (the language, not the runtime) rather than the library itself.

[ILikePie]

What's wrong with my tree nodes?

Code: [Select]

typedef struct _node {
  int weight;
  node* left;
  node* right;
} node;
Compiling gives me this:

Code: [Select]

huff.c:8:3: error: expected specifier-qualifier-list before ‘node’it refers to the "node* left" part. What's a specifier-qualifier-list, and why can't a struct contain more of itself?

e, Wait, it should be "struct _node* left", never mind.

[TolyK]

C++?
shit, can someone explain C++ tree building in a spoiler? i'm kinda lazy to look through the thread of 60 pages

[ILikePie]

That's C actually. I'm still trying to work it, but in order to build a tree you need a node struct, like the one I've got on top:

Code: [Select]

typedef struct _node {
  int value;
  struct _node* left;
  struct _node* right;
} node;
Create, say, three nodes, and link them together:

Code: [Select]

node a,b,c;
a.value = 5; b.value = 1; c.value = 2;

a.left = &b;
a.right = &c;
Now b and c's left and right nodes can be accessed with, if I remember correctly, a->left->left. Correct me if I'm wrong, it's been a while, and I've never done trees before.

[Nadaka]

Its been forever since I did c/c++, so take what I say wit a grain of salt...
(*foo).bar is the same as foo -> bar

so (*(*a).left).left is the same as a -> left -> left