Archived

This topic is now archived and is closed to further replies.

Jonus

OpenGL How do i start my own OpenGL GUI?

Recommended Posts

How would i design a gui? How does this message queue thing work? What classes will i need? I an working on an startegy game, and i need imput on how to do my gui right!

Share this post


Link to post
Share on other sites
heres a quick sample. no guarantee on it working, or being good. just ideas. I hope this helps.


class Button{
public:
//give it variables
float left,right,top,bottom;//relative to window
char *name;
//and a callback function
int (*fn)(void);
}

class Window{
public:
//give it variables
float left,right,top,bottom;
char *title;
int nButtons;//number of buttons
Button *buttons;//pointer to buttons in this window
//and functions like:
void Load(char* file);
void Draw();
}

Share this post


Link to post
Share on other sites
Still need more info on that message queue thing...

@robirt
Ok that helps a bit, but what's a call back function?

[edited by - Jonus on August 13, 2002 8:20:52 AM]

Share this post


Link to post
Share on other sites
I have also been working on some GUI-Elements like Buttons and Scrollbars which are implemented with OpenGL. I can tell you how I have designed that things. First I have introduced a common Baseclass which i named GraphicObject. This class contains all attributes and methods every Graphical Object have. Then there are some specific basical Graphical-Objects Classes which are inherited from the GraphicObject-Class, like a simple Line or a Rectangle and so on. Then I introduce a Composite-Class which contains of many different GraphicObjects(Here I use the Composite-Pattern for Details see E.Gamma,... "Design-Patterns"). A button or another GUI-Element is a Composite of different GraphicObjects like lines, rectangles and so on. So I created a Button-Class which inherits the Composite-Class.
For the Message-queue thing I use the Chain of Responsibility-Pattern (also see E.Gamma, ... "Design-Patterns" for more Details). That means that every GUI-Element has a method like HandleEvent() which get the Input like Windows callback Function and inside this you can Handle every Event. Do this for every GUI-Element and even the Window-itself(The Window is a composite of other GUI-Elements). For setting-up the Messagequeue call in your Windows-Main Function the HandleEvent()-Functions of your Window(s) which delegates the Event to their Child-Objects.
This is one Idea how you can implement your GUI in OpenGL. It is not an easy things and maybe there exists easier Designs. Look at www.OpenGL.org there exists alrady some GUI-Interfaces for OpenGL perhaps to use such an Library would be easier as implementing your own GUI.
Good luck

Peter Gmeiner

Share this post


Link to post
Share on other sites
a callback function is a function you set up to be called by another function, to answer both questions, the messages sent to you by your OS are usually handled by a callback function. In windows, when youre setting up your window class, you specify a function that will be called everytime you need to deal with a message you get from, and code that function accordingly. For a rundown on the whole thing, go to www.winprog.org and/or www.gametutorials.com

Share this post


Link to post
Share on other sites
Thanks guys!

@PGmeiner
I will take a close look at the design patterns your taleked about!

The case study at the beginning of the book is very intressting too.

@digitec devil
I still don''t understand what a ''callback'' function is, but i guess i will make it without it.

They''re function pointers in c and virtul in c++, thats all i understand until now.

@Michalson
I will check it out, ... cool that i can program a bit dx ... and yes i skiped part 1 .

Bruno
I will take a look at his source, but i don''t think thats his stuff is what i am looking for.

Share this post


Link to post
Share on other sites

  • Announcements

  • Forum Statistics

    • Total Topics
      628350
    • Total Posts
      2982211
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now