Quote: "I disagree, altough I'm working with DX now, it's just not as simple to set up as OGL, and the code looks horrible becouse of it being object orientated "
Why not?
DirectX you include the library header, make a Window, create the DirectX Instance. voila, setup.
You can then attach that to a class and create as you deem necessary.
OpenGL you include the library header, make a Window, create the resize routine, create the exit routine, create the render routine, setup the context, setup opengl, initilise.
OpenGL might be more procedural, but that is because it is. This means an engine will end up being many times more code than a DirectX one.
Tell ya what, i'll code up 2 versions of the same example in OpenGL and DirectX and show you; be the simplist route here.
Quote: "I remember when people said VB dll's were impossible to get working in DBP, but then CR,Exeat and a few others made it possible."
I remember people saying it wasn't possible to Directly use Visual Basic 6 DLLs; and ya know what, we were right
Quote: "I remember when people said OOP wouldn't be possible ever in DBP, well, TheWendigo is working on this and has already shown working examples of DarkBasic OOP."
I remember the discussion about it saying it wasn't worth the benifits. The overhead for it would've been too much with a language which was already trailing speed-wise to competitors.
.. People seem to think OpenGL is the answer to alot of prayers, i just think your going to be very disappointed.