Switch to OpenTK

[GoogleCodeExporter]

With TaoFramework being old and decrepit, should MonoXNA switch to OpenTK?

I've been constantly having issues with TaoFramework on mostly newer GPUs, so 
I'll be working on my own branch to have it replaced with OpenTK as it is more 
actively supported.

If you guys want, I can push this out onto the repository as soon as I get it 
working.

Original issue reported on code.google.com by ali.scis...@gmail.com on 21 Nov 2011 at 6:40

[GoogleCodeExporter]

I've been thinking about this myself, but I haven't had the time to look into 
it. Feel free to make the changes necessary.

Original comment by lav...@gmail.com on 22 Nov 2011 at 8:52

[GoogleCodeExporter]

I've made the quick switch on a base branch of MonoXNA and the performance 
seemed to have degraded. This might be just because of OpenTK having a much 
better debug assemblies and they actually check for errors on every OpenGL call 
you make, but I'm not really dismissing my sloppy port either. Is there a 
profiler of sorts for .NET/Mono?

Original comment by ali.scis...@gmail.com on 15 Dec 2011 at 8:41

[GoogleCodeExporter]

Beyond Microsoft profilers, I tend to use SlimTune 
(http://code.google.com/p/slimtune/). It'll help track memory usage as well as 
run-time costs. If you can post your changes (as a patch or a fork on git or 
something) I can take a look and see if I have the same issues.

Original comment by gurwinde...@gmail.com on 22 Mar 2012 at 3:27

[GoogleCodeExporter]

I think this points to the OpenTK branch I've made

https://bitbucket.org/alisci01/monoxna/src/5a02ce836692

Most of the fringe development happens in the EffectPipeline branch, so I 
haven't had much time to look into OpenTK.

Original comment by ali.scis...@gmail.com on 22 Mar 2012 at 4:43