(2012-08-14 22:15)bobo1on1 Wrote: Hm, I guess that makes me a code monkey?
Bobo? You're secretly a dev? So you really were messing with me!
(2012-08-14 20:51)Bstrdsmkr Wrote: I'm not a skinner so this may not be possible, but could you skin the audio settings panel and "fake" multiple pages? I'm thinking hide all the elements, then show all the elements for the next "page," which to xbmc is still just the audio settings page.
Well, i kind of want to minimize the amount of pages used. And remember, settings is still there. This is just to get people up and running WITH the wow factor, as fast as possible. Asking only a hand full of questions and deduction all the possible settings we can set for them based on that.
(2012-08-13 16:50)Martijn Wrote: Why not just open the audio settings panel?
All settings are there and no dirty hacks needed. It should be possible to open it with a button or script.
Frodo select the 'best' setting and user maybe has to adjust output device.
Dirty hacks will be needed for everything as long as the idea is to apply all the settings on exit (if the user is sure).
Which i would prefer because some of the "next" buttons actually change settings. Otherwise just having a look through setup is not possible without making changes. But it is because of using the "next" buttons this way, that you can have so little buttons for many settings.
The alternative would also be dirty as it would either have to backup settings files and upon "don't apply" copy them back.
How much can Frodo set for a user? Everything it can do, the setup won't have to.
But it would not even be that dirty, as my plan was to write the normal <onclick> commands, all to one file.
And on the last click, the file with all the other clicks runs.
Or use the same system as the Advanced Settings Editor (dom).
Or hoping for better suggestions.
But don't forget, this was not my idea. But i had seen this asked for many times. So i thought, well if i just start photoshopping, some other suggestions will pop up. And when i got into it, i thought well lets just try to make a "from GUI to code" design rather then the "from code to GUI" we have now. And see if anything interesting rolls out. I for example really like the way source + content gets set by one "browse to folder".
Here is a pic of the apply everything at the end, when you are sure, page.
Ok, so i looked at the audio again and made a new suggestion.
The separate sub button is not "needed". It's not that much easier, but we have the space atm.
It would only catch people that don't know 5.1 means 5 speakers + sub. But if we can, why not?
Then listing the wasapi, s/pdiff, ect choices. Showing them like this, as changes to the defaults.
(that people don't even need to know the names of). Gives oversight, allows for (i believe) all combinations.
And can (upon reading the explanation) probably be skipped by thinking "I've never heard of those".