[yast-devel] redesign of webyast users module
![](https://seccdn.libravatar.org/avatar/410d759ade7bffbfb7343df9e4bbc85a.jpg?s=120&d=mm&r=g)
Hi, please find some ideas for a redesign of webYaST`s "Users" module at: http://home.arcor.de/martin.schmidkunz/ (wasn`t sure if it is a good idea to store all the jquery stuff in my Export...) It is based on rlihm`s mock up (http://gagarin.suse.de/). The basic concept is to show only the most important table entry on a top level (e.g. user name). Therefore there are fewer elements on the screen which eases the use of the module and increases its self-descriptivness and its task orientation. On a second level which the user accesses after clicking on the user name the user can choose whether to "edit" or "delete" the entry. Again it is avoided to show non-task related information. Before deleting an item the user is prompted an "Are you sure?" pop up in order to increase error tolerance and prevent the user from unintended data loss. "Edit" shows the settings of the list entry. If more settings are available they are organized in tabs. The "Edit" dialog is left either via "Save" or "Cancel" New list entries can be added via "Add New Item" button on top the list. Concerning "basic concept" * "Save"/"Cancel"/"Add" do not work properly in the mock up * "Add" should be a wizard * User needs to click "Save" twice (once in the edit tab and then in the main window) I am not sure whether this is intuitive. What do you think about that? * list should be sortable but I am not caple of implementing this technically Concerning "Users" module * When adding a user currently there are 8-9 settings which needed to be adjusted and some of them seem quite obscure to me. So, what do you think: which settings should be really editable via GUI? Currently there are: Full Name Groups Default Group (GID) Home Directory Do not create home directory Login Shell Login Name UID Number Password Full Name, Login Name, Password and Groups seem quite clear to me but is it really necessary to set login shell and UID in the GUI? And home directory? Wouldn`t it make sense to have a sane default which could be edited via an editor? * What do you think about showing permissions in the users module as well? This would seem quite logical to me. What is the reason, why permissions and users are separated? Do you have any other topics concerning users module GUI? Looking forward to your comments! Best regards and have a happy 2010, Martin ---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. Novell® Making IT Work As One™
![](https://seccdn.libravatar.org/avatar/3fc7d50720d07e9a5b41177d39904308.jpg?s=120&d=mm&r=g)
Am Dienstag 29 Dezember 2009 11:05:46 schrieb Martin Schmidkunz:
Hi,
please find some ideas for a redesign of webYaST`s "Users" module at: http://home.arcor.de/martin.schmidkunz/ (wasn`t sure if it is a good idea to store all the jquery stuff in my Export...) It is based on rlihm`s mock up (http://gagarin.suse.de/).
[..]
Do you have any other topics concerning users module GUI?
I am unsure about the use case of the Users Module in WebYaST. How many users do you expect to be managed through it? Should it support LDAP based users like yast2-users? If yes, then it might need to handle quite a large amount of users (thousands?) e.g. by providing functionality to search for a specific users and/or to filter the list by certain criteria instead of always showing all available users. If it is only intended for managing local /etc/passwd users such things are probably not needed. regards, Ralf -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/d18d0fd84170a8255c30388a800b96c8.jpg?s=120&d=mm&r=g)
* Ralf Haferkamp <rhafer@suse.de> [Jan 07. 2010 11:49]:
Am Dienstag 29 Dezember 2009 11:05:46 schrieb Martin Schmidkunz:
Hi,
please find some ideas for a redesign of webYaST`s "Users" module at: http://home.arcor.de/martin.schmidkunz/ (wasn`t sure if it is a good idea to store all the jquery stuff in my Export...) It is based on rlihm`s mock up (http://gagarin.suse.de/).
[..]
Do you have any other topics concerning users module GUI?
I am unsure about the use case of the Users Module in WebYaST.
Well, we're requested to deliver it. But I share your view ;-)
How many users do you expect to be managed through it?
How many users will be accessing an appliance ?
Should it support LDAP based users like yast2-users?
No. The current scope explicitly limited to /etc/passwd.
If yes, then it might need to handle quite a large amount of users (thousands?) e.g. by providing functionality to search for a specific users and/or to filter the list by certain criteria instead of always showing all available users.
If it is only intended for managing local /etc/passwd users such things are probably not needed.
Agreed. 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
![](https://seccdn.libravatar.org/avatar/410d759ade7bffbfb7343df9e4bbc85a.jpg?s=120&d=mm&r=g)
If it is only intended for managing local /etc/passwd users such things are probably not needed.
Which functions are covered by this scenario? Username, Password and....? Best regards, Martin ---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. Novell® Making IT Work As One™
![](https://seccdn.libravatar.org/avatar/d18d0fd84170a8255c30388a800b96c8.jpg?s=120&d=mm&r=g)
* Martin Schmidkunz <mschmidkunz@suse.de> [Jan 11. 2010 14:19]:
If it is only intended for managing local /etc/passwd users such things are probably not needed.
Which functions are covered by this scenario? Username, Password and....?
The basics of Linux user management - name - uid - gid - home dir - shell See the 'useradd' command in Linux And a basic group management - name - gid - list of users (uids) belonging to this group 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
![](https://seccdn.libravatar.org/avatar/3fc7d50720d07e9a5b41177d39904308.jpg?s=120&d=mm&r=g)
Am Donnerstag 07 Januar 2010 13:47:22 schrieb Klaus Kaempf:
* Ralf Haferkamp <rhafer@suse.de> [Jan 07. 2010 11:49]:
Am Dienstag 29 Dezember 2009 11:05:46 schrieb Martin Schmidkunz:
Hi,
please find some ideas for a redesign of webYaST`s "Users" module at: http://home.arcor.de/martin.schmidkunz/ (wasn`t sure if it is a good idea to store all the jquery stuff in my Export...) It is based on rlihm`s mock up (http://gagarin.suse.de/).
[..]
Do you have any other topics concerning users module GUI?
I am unsure about the use case of the Users Module in WebYaST.
Well, we're requested to deliver it. But I share your view ;-)
How many users do you expect to be managed through it?
How many users will be accessing an appliance ? Depends on what "accessing an appliance" means here. If you talk about accessing it through the WebYaST interface, I guess we are talking about a very limited set of users. If we talk about the users that access the appliance by other means depeding on the appliance the number can be quite large I guess :).
Should it support LDAP based users like yast2-users? No. The current scope explicitly limited to /etc/passwd. Are there any plans to extend that to external sources at some point? I can think of use cases where it might make perfect sense to allow WebYaST Users being managed in a Directory. The access policies might fit there as well.
If yes, then it might need to handle quite a large amount of users (thousands?) e.g. by providing functionality to search for a specific users and/or to filter the list by certain criteria instead of always showing all available users.
If it is only intended for managing local /etc/passwd users such things are probably not needed.
regards, Ralf -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/d18d0fd84170a8255c30388a800b96c8.jpg?s=120&d=mm&r=g)
* Ralf Haferkamp <rhafer@suse.de> [Jan 12. 2010 16:37]:
Should it support LDAP based users like yast2-users? No. The current scope explicitly limited to /etc/passwd. Are there any plans to extend that to external sources at some point?
I'm not aware of any.
I can think of use cases where it might make perfect sense to allow WebYaST Users being managed in a Directory. The access policies might fit there as well.
Oh, absolutely ! First things first, so lets focus on the simple case for now. 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
participants (3)
-
Klaus Kaempf
-
Martin Schmidkunz
-
Ralf Haferkamp