Test Framework classes either require or propogate std and JPH namespace inclusion

[Avelina9X]

I've been utilising the Test Framework debug renderer and Application classes to bootstrap engine development without needing to implement my own renderer backend. This has had some unintended side effects, however, because certain headers will either propagate a header level using namespace std/JPH while other headers will throw errors because they assume using namespace std/JPH has been specified earlier.

One such example is TestFramework/Renderer/Renderer.h which will cause any file that includes this header to fail compilation unless the JPH and std namespaces were specified prior to including the header.

And of course we have TestFramework/TestFramework.h which has three using namespace specifiers (and one using specifier for ComPtr).

If this is a design decision made purely because the Test Framework was never intended to be used externally I will of course close this issue... but the JPH debug renderer is honestly really good, and using it for early development is a no brainer because it quite literally implements everything for you.

[jrouwe]

The test framework was not intended to be a reusable part of the library. It was purely made to run the examples.

If you want to have a simple debug renderer, you can use DebugRendererSimple. This class only requires implementing 3 functions which should be really easy if you have a renderer of your own.

That said, I've seen multiple people copy paste these classes into their own projects and you're free to do so and hack it towards what you need.

I've done a quick check, and getting rid of using namespace std is not too bad. Getting rid of using namespace JPH is a lot of work, and not something I'd want to do.

[jrouwe]

I've removed using namespace std from TestFramework in fe0b87a

[Avelina9X]

Perfect, thank you for your work!