ppl. consider to participate in the UI design proper: what and how you would like to see and behave in a (new?) track/bus properties dialog? that might or should be a good start. consider some mockups, hand drawings, whatever :) should it be a brand new formula?
take ones personal note before you start arguing: "wizards" are out of the question. period. please. let's not be too paternalist to n00b users. this is niche software and my stance is: the user is in power of the software. not the other way around. yeah. we've all been n00bs once i know, but then, keyword is once. and then, about twice, you get over it, you start doing things your own way, isn't that so? and that's awesome. you just don't need a "wizard" to remind you when you were (once) on the verge of a clueless stupidity state, do you? :)
so, the tickets are there:
ppl. consider to participate in the UI design proper: what and how you would like to see and behave in a (new?) track/bus properties dialog? that might or should be a good start. consider some mockups, hand drawings, whatever :) should it be a brand new formula?
take ones personal note before you start arguing: "wizards" are out of the question. period. please. let's not be too paternalist to n00b users. this is niche software and my stance is: the user is in power of the software. not the other way around. yeah. we've all been n00bs once i know, but then, keyword is once. and then, about twice, you get over it, you start doing things your own way, isn't that so? and that's awesome. you just don't need a "wizard" to remind you when you were (once) on the verge of a clueless stupidity state, do you? :)
nuff said. let the ideas flow
cheers