• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
solenoidz

GUI internal implementaion - widgets, pages

4 posts in this topic

Hi people.
For my ingame user interface I have implemented a textured object, that acts like button, has onMouseOver(), onClicked() , events etc.
Right now for every single object of that type, I have a property for the page it belongs. I.e. the Main menu widgets have page property set to 0, the Options widgets have their page propery set to 1 etc. Then, when the user press for example hit "escape" I set the page number to 0 and draw the widgets that have page property set to 0, when the user click on Options I set the page index to 1 and draw widgets that have page 1 etc..
This works but I have a feeling that it isn't flexible and could cause a lot of interating over the widgets list to draw only the elements that match the current page.
I think there might be better practices to implement GUI systems. For example, make separate list of widgets fort every page. Something like
GUISystem{
std::vector<Widget*> mainPage ;
std::vector<Widget*> options ;
}

and then interate the appropriate list and draw elements.

Is there other better approaches ? How do you guys will implement such a GUI system ?

Thanks.
0

Share this post


Link to post
Share on other sites
"myGUI" has all state of the art features you expect from a GUI. why re-write everythin from zero? You have just to provide drawing functions, all other logic is handled for you.

write a good GUI system is almost hard as writing a good 3D engine. untill you need a button and some text is feasible, but more complex stuff will get harder and harder

anyway a system like your should be a list of lists. So only one list is active at a time. Unless you are going to have hundreds elements for each list, iterating every element is not very heavy operation.

Then if you are going to have many elements, probably is better to also have a "I Am Here" index so that iteration starts from the first visible element instead from the begin of the list. (also using a grid is very nice so that screen is divided into quads and each element is indexed by (X,Y) instead of by (IDX).

(by the way, the active list is already a "I Am On This List" stuff) Edited by DemonRad
0

Share this post


Link to post
Share on other sites
I've recently been implementing a GUI.

Instead of having a list of widgets, I used a tree structure. I.e. each object is a node, and has a parent, and can have children. The implementation I wrote is fairly similar to a 'scene graph' which is often used in 3d engines / 3d modelling tools.

If you use this 'parent child' relationship you can make coordinates relative, and have the position of widgets / objects relative to their parent. So when you move e.g. a dialog box all it's child controls also move automagically.

You can also easily 'cull' off branches of the scene graph just by setting a cull flag on a branch, and recursive updates / renders etc will go no further, and update / render only bits that you have changed (instead of trying to render the whole GUI each frame).

[quote][color=#282828][font=helvetica, arial, verdana, tahoma, sans-serif][size=3][left][background=rgb(250, 251, 252)]write a good GUI system is almost hard as writing a good 3D engine[/background][/left][/size][/font][/color][/quote]
Not in my experience.
0

Share this post


Link to post
Share on other sites
Thanks guys.

[b] [url="http://www.gamedev.net/user/195158-demonrad/"]DemonRad[/url], I don't know what's wrong with me, but I prefer make things myself. myGUI looks nice, but I prefer more C-like code style. myGUI looks heavy Ogre influenced at first glance.[/b]




[b] [url="http://www.gamedev.net/user/196788-lawnjelly/"]lawnjelly[/url] - thanks. My GUI currently isn't very complex, so simple textured alphatested, blended object with mouse events are sufficient, moreover I plan to use a game launcher that will implement using operating system controls most of the graphics, sounds options, sliders etc. A hierarchy you descibed is easily implemented and I consider making the step in that direction when the time comes.[/b]
0

Share this post


Link to post
Share on other sites
[quote name='lawnjelly' timestamp='1341672854' post='4956650']
I've recently been implementing a GUI.

Instead of having a list of widgets, I used a tree structure. I.e. each object is a node, and has a parent, and can have children. The implementation I wrote is fairly similar to a 'scene graph' which is often used in 3d engines / 3d modelling tools.

If you use this 'parent child' relationship you can make coordinates relative, and have the position of widgets / objects relative to their parent. So when you move e.g. a dialog box all it's child controls also move automagically.

You can also easily 'cull' off branches of the scene graph just by setting a cull flag on a branch, and recursive updates / renders etc will go no further, and update / render only bits that you have changed (instead of trying to render the whole GUI each frame).

[quote]
[left][background=rgb(250, 251, 252)]write a good GUI system is almost hard as writing a good 3D engine[/background][/left]
[/quote]
Not in my experience.
[/quote]


When you have to support several different econdings, and gui serialization with a decent GUI editor yes ;-). I prefer too do things myself. Anyway if you already done scene graph stuff, half of the work is done for the GUI.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0