Optimal GUI pipeline?

Danzo

I was just wondering if anyone had ideas about the best way to go about designing and implementing a GUI or have a good resource that goes through the process from start to finish. Maybe as well as resources on how to go about actually creating the graphics as well.

Also, and this is more of a programmer question, is it possible to change the layout of a GUI once it is already established initially and if so, is it much difficulty and extra cost? Some developers I am working with now are adamant that once the layout is established it can not be changed without serious overhaul to the code which I find a bit odd.

Thanks for any help you guys can provide.

passerby

What is this for, with qt uis its pretty easy to modify the whole ui after runtime.

Danzo

I don't know enough about programming to say but from what I know the developers are developing this app, which is a quiz game, using C++. The developers are not on location and I have to correspond with them. I was a bit startled by their inflexibility to change the UI after I submitted the initial design.

I was just wondering exactly how much effort is it to change the UI? Would it need lots of recoding or are they just working with an inefficient workflow. Because they did say that it would increase dev time significantly to re-do the layout which I find very bizarre.

.nL

The best answer in this case, is 'it depends on what they're using for the UI'.

From a personal point of view, GUI programming is amongst the most mind-numbingly unpleasant things I've ever done, even with something as good as QT. It's a bit like scraping something sharp against a chalkboard. I'm not sure if it's the same for other developers or not.

ProperSquid

I enjoyed doing UI design with Qt. As for the programmers, it really depends. If they had to roll their own GUI solution, then I can see it taking a while. But, as everyone said, depends on what they are doing with the UI.

iniside

.nL wrote: »

The best answer in this case, is 'it depends on what they're using for the UI'.

From a personal point of view, GUI programming is amongst the most mind-numbingly unpleasant things I've ever done, even with something as good as QT. It's a bit like scraping something sharp against a chalkboard. I'm not sure if it's the same for other developers or not.

+1
I've been recently coding UI, because looking at how game mechanics behave in debugger constantly really is no longer that fun (not to mention efficient). Not to mention thing I'm using for coding UI have very little documentation and explanation how it works. But I have little choice here.
The sooner I get something that even barerly works and show information I need I'm done with it, for time being.

As for OP question. It's very dependant on what is used to code UI. And more over how it is coded.

passerby

Like everyone stated we need more info, what engine and what GUI framework.