* Martin Schmidkunz <Martin.Schmidkunz@gmx.de> [Feb 22. 2010 14:35]:
Hi!
Thanks for all your comments!
Concerning hide/show behaviour: There is already a basic overview concept created by Robert Lihm (gagarin.suse.de): On hover the basic actions (edit/delete) are shown and then executed on click. I didn`t use this mock up because it was too complex for my skills (e.g. it used three different style sheets) I will add it to the style guide in the next days.
Thanks ! As said in todays status call, I have meanwhile received the code from Robert and will push it to WebYaST in the near future.
Enable/disable: Why not use a check box? The reason is that check box has a relative small target hit area compared to a button. Secondly combined with explanatory status text a labelled button seem to be more easy to understand.
I fully agree here. My initial thought also was using a checkbox. However, enable/disable trigger a modification request. Modifications are to be presented as buttons for consistency reasons.
"Keep downloaded packages" Is this really something for the GUI? Compared with the settings level in other module this seems quite complex to me.
Agreed. Certainly too complex for our primary target group. Lets move such details out of the main dialog. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org