<clarkbw> the keyboard model chooser had a problem...
<clarkbw> my note says the resize of the capplet when you open the drop down
<clarkbw> let me try it out again
<clarkbw> oh wow, now i remember
<clarkbw> we need a better way to do this :-\
* clarkbw gets screenshots
<svu> Agree! The button suxx
<svu> The button "Reset to defaults" should be put somewhere else. Where?
* svu is listening to the expert's opinion
<clarkbw> http://clarkson.edu/~clarkbw/screenies/Screenshot-Gnome-keyboard-properties.png
<clarkbw> here's the initial
<clarkbw> http://clarkson.edu/~clarkbw/screenies/Screenshot-Gnome-keyboard-properties-1.png
<clarkbw> ^ that's what happens after i open the drop down list
<clarkbw> that needs to change
<svu> I know. I know. What would be the good UI here? Actually, even removing the button will not solve the problem completely - just make it less dramatic
<clarkbw> yes
<svu> So, two questions: where to get the bloody button, how to handle models.
<svu> Lets's start with #1 please.
<svu> The idea is to put the button at the bottom, below the trees.
--> ska-fan (~ska-fan@dsl-082-082-100-001.arcor-ip.net) has joined #ui-review
<svu> But in this case it will effectively eat the entire row
<svu> Just one little button... 
<svu> It does not look great really. 
<ska-fan> Are there people out there who like to make glade files hig compliant? :)
<jody> svu: resizable is good
<clarkbw> the current layout is good
<svu> Also, the semantical problem that this button on tab3 also affects tab4. I would call it question #1.a
<clarkbw> we just need to figure on how to change the choosing of the keyboard model
<clarkbw> svu, can you explain exactly how it effects tab4
<svu> well, probably if we sort this out, there will be no need to move the button. But it still lives us with #1.a:)
<clarkbw> just to be clear
<svu> Sure
<svu> The button takes the system xkb settings (written in XF86Config) and restores them. This affects the ENTIRE xkb configuration, which is actually what we have on tabs 3 and 4
<svu> Does this make sense?
<clarkbw> yes, so it triggers a reload on the treeviews
<svu> exactly
<svu> You got me right. And the models combo as well.
<clarkbw> and i'd say this is a configuration that's done maybe once in the life of the system
<svu> Well, kind of right. So what?
<clarkbw> because if it's only ever done once, then it's ok if we make it slightly harder to do in the name of looking good :)
<svu> What do you mean? |-|
<clarkbw> i.e. the drop down for the keyboard model suggests that you can switch quickly and easily between models
<clarkbw> but if people aren't going to switch quickly or often, then why are we making this choice?
<svu> Yes. Kinda...
<svu> sry, which choice? Choice of the keyboard?
<svu> do not get you really
<clarkbw> the choice of widget for displaying which model
<clarkbw> instead we could just use a label with a button going to another window for choosing models
<svu> ok. what's your idea? text field?0:-)
<clarkbw> that is a for instance
<svu> Another window?
<svu> Just for one combo? It would look strange I'd say...
<clarkbw> well since we can't control the length of strings in the combo
<clarkbw> we need something else that doesn't bork our layout
<clarkbw> seth, any ideas for this?
<svu> well, I could cut strings on some fixed length - but it suxx
<seth> whoops
<seth> reading back
<seth> hmmm
<seth> I don't have any particularly bright ideas here
<svu> :/ Will we broadcast the question somewhere?
<svu> Is there anything in gtk which would prevent combo from enlarging?
* svu thinks about single-sel list with both vert and hor scrolls and finds is damn ugly
<clarkbw> jody, this is a far off one, but i'll send it anyway :)
<clarkbw> jody, http://clarkson.edu/~clarkbw/screenies/gnumeric/insert.png <-- more feedback for inserting
<clarkbw> svu, i'm not sure about gtk keeping the widget size normal
<clarkbw> anyway, this is quite the edge case; but something that should be filed as a bug
<svu> Not critical I hope? Against g-c-c or agains gtk?:)
<clarkbw> all ui-review bugs get filed as minor severity
<clarkbw> hm, this would be against the capplet i think
<clarkbw> but we could ask gtk people about how to fix it