<html><head><meta name="Generator" content="PSI HTML/CSS Generator"/> <style type="text/css"></style> </head><BODY BGCOLOR="white" ><div>Dmitri,</div> <div> </div> <div>In my opinion, the tabs are a good solution:</div> <div> </div> <div>- when they're ajaxified, i.e. no reload of the page when changing tabs, otherwise expandable sections are preferable</div> <div>- when the tab pages have the same height so you find quickly the action buttons at the bottom of the tab pages </div> <div> </div> <div>But really, the user page as it is is fine to me, provided you implement that 2nd column and display some basic info about the group membership of the user with a couple of links like 'add', 'remove'. And I must say I like its simplicity. I will also review the other documents you attached and keep you updated about my thoughts.</div> <div> </div> <div>Eric. ============================================================= Hi Eric, Thank you for getting back. We will play with it and see what makes sense. When we have something to give a try we will post it on the site. I like the "unlock" idea on per fields basis. The groups and other "memberships" will be on the separate "tab". We now plan to have one "tab" with personal information and another with: gorup memberships, netgroup memberships, delegations, roles etc. Dmitri Eric wrote: > Hi Dmitri, > > I agree that having to uncollapse too many sections becomes tiring if > not confusing (a Drupal syndrome in their administration). The ideal > case would give the administrator the option of hiding the fields he > or her uses the less often in a menu 'Preferences'. > > I don't mind scrolling either, but with modern screens having great > resolutions, using 1 column only leaves an enormous amount of white > space to the right. I think a 2nd column would give a sense of > balance. I'd also like to see to which groups the user belongs too, > and you could use the 2nd column for that purpose. > > I personnally don't understand the real purpose of the 'edit protected > fields' flag. To me this application is targeted to application > administrators who know what they do. Anyway, if this field has to be > there, I think a better place would be next to each protected field > and be represented by a link next to Add, Delete, and be labeled 'Unlock'. > Eric. > > ============================================================= > Hi Eric, > > Thank you for your feedback. > It is interesting that we asked about collapsing or not collapsing > sections on the page and also about making it two columns. > Everybody we asked said : > a) I want to see everything at once - less clicking the better > b) I do not mind scrolling - two columns will make the page too overloaded > > But this is their opinion. Yours is the opposite. It would be > interesting to learn more about your "clicking habits" and UI preferences. > > The other comments make sense to me : > a) Password reset link > b) Buttons per section > > May be "edit protected fields flag" should be in the section too rather > than one per page? > > Thanks > Dmitri > > Eric wrote: > > Update User: > > > > My overall opionion is that the page is too long, and several fields > > should be collapsed by default. It feels unatural to see the action > > buttons 'Delete User', "Cancel', 'Update User' at the top right of the > > page content. I believe they should appear at the bottom right of each > > sub-sections. I also think a 2-column display would be more appropriate. > > > > Identity Details Account Status: > > First Name: Username: > > Last Name: (Collapsed) Password, UID, GID, Home directory, Login > > shell, Gecos > > Title: > > Work number: > > Cell number: > > Email: > > > > Additional: (Collapsed) Fax, Pager, Full name, Display Name, Initials. > > > > Mailing: (Collapsed) > > > > Employee Info: (Collapsed) > > > > Misc info: (collapsed) > > > > > > Password: I would only display a link: 'Reset password', then the 2 > > boxes would appear > > Add links: I would not repeat the field name, and I would also put the > > delete link next to it: 'Add Delete' > > > > > > Eric Desgranges > > eric@vcardprocessor.com > > </div> </body></html>