Interface Design and UX Thread - How our App Looks

[angelize]

I like the Gear interface. I took Barbara's file and gave it a grungy metal look. All the pieces and parts and a couple of really nice textures as well came from the scrapbook section of the DPX designs gallery. I modified them a bit to fit Barbara's basic idea.

[Barbara B]

I like what you did.

I especially like the current tab displaying in a metal nameplate or gauge window, the addition of the screw heads.

I didn't texture the gear, especially the center panel because I thought it would make the text hard to read, but your treatment separates beautifully.

[Rik]

Are we settled on the Wheel, or is it worth considering a different look?

Obviously, the colours can be changed to suit.

[PeteS]

Personally, I really like Rik's design. A good, clean, clear UI. And more importantly is scalable if new options are needed in the future, the UI design doesn't need re-vamping.

Barbara's design bought back memories of Webstyle 4 for me with the layout of the sections (except the editing options in the middle). Nice design and some good designs it's inspired Gary (I like the white on blue design) and Francis

As this project is in a fledging state I think that getting the basic functionality of the program figured out is the first step, and even just the functionality implemented for the first release. That will give us an indication of the specific requirements of the UI (eg how much space is needed for each section, how many sections etc). Also, the UI is largely superficial - it's a skin that's applied. Much like changing your CSS on a website (OK, may be it's a bit more work, but you get the idea).

[Gare]

If all this does is serve as a reinforcement that the tg community is behind the project and behind Grace, I feel it was an effort worth expending.

Yes, Pete is dead-on: skinning is trivial compared to the coding, but it is nice to see both cooperative and independent ideas being brought up.

Food for thought!

-g

[gracehjs]

The actual coders decided that we would like to start with a basic design and get the functionality there. I actually like RIKs take better initially for the content. I would like to add a field for each item that showed it had been changed from the default value - I think this would be helpful.
Plus, as I pointed out this is a standard windows app and as such should have the standard controls for menus. Look at the one I proposed.

[mwenz]

Grace,

Design by committee is rarely efficient and at this stage is rather distracting. Having done large-scale programming in the past, I feel you are on the best track to make it functional in all aspects, followed by likely reorganization (moving controls to different tabs, renaming controls, etc.), and then gather all the ideas on appearance and making a decision as to where you take it.

If I were the programmer here, I would leave the appearance-oriented threads to develop and probably not even take the time to comment on them. It is incredibly premature--but then, appearance issues are the easiest part for most designers.

Mike

[gracehjs]

I really like this look and I think it is quite doable.

Are we settled on the Wheel, or is it worth considering a different look?

Obviously, the colours can be changed to suit.

[angelize]

I've played around with Rik's basic design with different colours. I came up with a set of harmonious colours using red, a soft warm grey and some darker greys. I also used black and white text in some areas.

[pauland]

Personally, as an observer, I really dislike the red.

Red is really bold and associated with danger, so on something that can do no harm, the idea of using red to highlight options can have a subconscious message - do this with care/don't do this.