search

sbarisic / NuklearDotNet

.NET binding for the Nuklear immediate mode GUI
Other
188 stars 15 forks source link

Status Questions #21

Open pha3z opened 3 years ago

pha3z commented 3 years ago

Extremely interested in building with this library. I have a couple questions:

1) You mention wanting to add support for multiple contexts. I am am pretty much a low-level OpenGL newbie. Is it a big deal to be able to add support for multiple contexts? What would be required? I would like to render a regular 3d scene and then use NuklearDotNet to render the GUI on top. Is this not achievable right now?

2) Seems a bit weird that you're still on .Net Framework. Is there a particular reason for that? I would presume that most people interested in this library are looking for something to use for cross-platform (.net core) immediate mode gui application.

If I can contribute, I will do so. Not quite sure yet, how useful I could be until I get my feet wet.

Donaut commented 3 years ago

What you want is totally doable. First, render the objects you want then render the Gui is that simple. But for cases where you want to render to a smaller nuklear window that can be resized, I don't think is there an easy way.

sbarisic commented 3 years ago

By multiple contexts i mean multiple separate calls to NuklearAPI to draw two separate instances of the GUI from one process. This is graphics API independent, this is why you have to implement your own class that inherits NuklearDevice (or copy one of the examples). You can draw it on DirectX, OpenGL or whatever.

.NET framework indeed is a curious choice, but everything should work on other platforms just fine if you compile it. I did not try it myself, as most of my projects are still regular .NET framework. The binaries work on new .NET just fine tho.

I will expand on my answer later, i have limited time now. And yes, i do accept contributions 😄