Opinions on GUI style
Okay I thought it would be a good idea to find out exactly the types of user interfaces people prefer before Silverwolf 2.0 coding gets too complete to back out of...
What I'm curious about is preferences for things like the main screen - is the preference toward a choosable list of items or items scattered as around the screen (like many skins with say a Honda logo in the middle with the buttons around it)?
So far, the MP3 module will be similar in function to v1.3 except that it's much more configurable, resizable and more skinnable. My question here - and this is probably the most important since it's probably the most important module for most people - is what type of layout is preferred; a scrollable listing a la v1.3 or more song info and fewer songs displayed at once?
I also prefer big easy to touch buttons - is that the consensus? Touchscreen is a new area for v2.0 since v1.3 was controlled by an RF remote which allowed for more screen real estate.
I'm just fishing for ideas because I have no imagination :)
I'm hoping I'll have v2.0 done within a couple months so it will be ready to install in our new minivan (ugghh yes a minivan... I had to grow up sometime I guess :) )
Any input/suggestions/screenshots/critisicm is appreciated!
Well.. I'll offer and opinion. I don't know what you mean by a choosable list, but I prefer where there are a few main buttons on the main page, allowing selection of catagory. Its nice to have a branded main page, but not nessecary.
On the mp3 section, I prefer fewer upcoming songs listed, and larger control buttons/current song info. Think IPod... the song selection should be a seperate dialog if possible.
Skinning is one of the hardest parts in my opinion. There is basic skin function, where you are simply changing the graphical appearance, yet buttons stay in the same position/size/function. I havn't figured out with QT an easy way to customize position/size/function of widgets. I'm sure it could be done... but it doesn't seem like it would be easy.
Okay that's helpful. I was debating on a scollable ("choosable" - poor choice of words :) ) list or something a bit more user friendly. I think I will also go the route you suggested with the MP3 player with having the song selection as a seperate entry module (I can't really call them dialogs since v2 won't be using any QDialogs).
What I'll be doing for the main screen (and likely other areas too) is simply defining polygons in the skin.conf file. Those polygons will be used in the mouseEvent() of the widget it's on to decide which "button" the user actually pressed.
I think you should do it in a mini information major information style thing. I've tried to show a little how I imagine it. Like if you're tooling around town and press the clock it would pop up the big clock and remove the small one from the mini info since the major info has it's focus now. Song and such as that would still be down bottom. Left the buttons would change to clock prefs or whatever that goes with the focus app. Then in mini info you press on the speed of your vehicle the nav pops up in major focus and clock goes back into mini with the left buttons dealing with nav options. Hope I explained myself ok.
EDIT: I almost forgot. What about adding some things alpha color like. I'm not sure what it's called but you could have in your main prefs some of your favorite colors and whatever the theme creator deemed that color didn't matter would change to that color. So chicks could have pink and purple and dudes red blue using the exact same theme with no direct editing files. Of course the text color would matter also so any text could be defined as well.
With some clever skin design many of the modules could be configured to work that way. Not a bad idea for some of the simpler ones.
As for alpha channels, every graphic, text and color element allows for an alpha channel. Colors and text colors are all defined as RGBA in the skin file, and graphics are simply designed that way by the artist as they see fit and all alpha channels are honored when they are drawn.
Once 2.0 reaches an alpha state I'm hoping there are some willing artists out there to create better skins than the default :)
Is it still going to be dependent on Gentoo, or can any distro use it now? I run Archlinux on my home pc. No car pc yet and your program is my deciding factor in which OS I install once I build the car pc. :) As far as the skins go I could give it a shot but I'd hate to promise the world and give you mediocrity.
It won't be tied to Gentoo or any distro in particular. I'm using SuSE on my development machines and Gentoo in the car.
I've already gotten an offer by a graphic artist to do a skin when it's ready so hopefully there will at least be two available :) by the time it reaches beta...
So far the only requirements are FMOD and Qt4 as far as actual libraries linked to the executable. I'll continue to use Xine for video.
- i'm comparing this to what i can see in the 1.2 pics on your page -
i suggest using a more common color scheme (less wild colors, more similar tone/temperature)
i don't like the gradient that's repeating over (like the blue,white,blue,white,blue column on the left side) - one gradient flowing through the whole screen, IMO, makes the picture calmer.
a more round font, the digits are hardly readable, at least that's what i think when i just quickly glance at them (like when driving)
touchscreen friendlyness is definately a must, as it doesn't make it any harder for people _not_ using a touchscreen - big buttons also allow a bigger font/pictogramme, which means better readability, which again means safer driving.
maybe you could post a picture of the skin you're using on 2.0 so we could directly comment on it
Check out the thread "SW2 Update"... Eventually I'll be posting pics on my site so as not to clog any threads here with pics.
Of course I'm hoping a better artist can develop a kick-butt skin when an alpha version is ready :)
The biggest difference between v1.x and v2.x from a user's perspective is that skinning was an afterthought in v1.x. v2.x started from scratch with skinning in mind so it's about 100 times more configurable. The skin configuration file is huge :eek: compared to the one for v1.x.
yeah i know how it is, i'm more of a coder than a skinner...my skins would look terribly bad..
after all a bad looking software is still more functional than a good looking skin without software ;)
i'll check out the given thread right after posting this.