SharpDX Toolkit emphasis, or not?

SharpDX Toolkit emphasis, or not?

rbwhitaker 04 Feb 2013 19:41

So I'm in the process of building some tutorials for SharpDX. They have an important piece called the SharpDX toolkit, which is a new part of SharpDX. It makes a lot of code look more like XNA.

But my question is, is that better? I know on one hand, it will make it easier for people to transition over, if they've been using XNA. But on the other hand, it feels like it may not be "pure" SharpDX. That there are probably going to be people who'd rather cut out the façade and get right to the core of SharpDX. I don't know which path to start with in my tutorials.

So are you a DX Purist, or an XNA Cloner?

Bob (guest) 10 Apr 2013 09:58

I vote for a more pure, barebones approach. No doubt, parts of the toolkit will probably be too useful to ignore, but the main gameloop, input capture etc… are all an integral part of game development, and it would be a shame to hide it away by the liberal use of a toolkit. And after all, if someone just wants XNA all over again, they can use mono. ; )