On Thu, 11 Jan 2001, Christoph Reck wrote:

> This is great! 
> Some comments follow.
> 
> Should the password be placed in a password field (to imhibit
> someone looking over the shoulder)? Normal applications also
> provide then a second confirmation field.

Do you mean on the login screen? If so, that has been changed
to a password field where what is typed is not visible.

Confirmation of password is a good idea, I will definitely add
that. Good eye.
 
> There should be a global user name (configurable, e.g. 'admin')
> that automagically owns all roles... To avoid accidental
> restricting the entry point. I guess this could be done at
> the application level (e.g. the admin app!).

Right now the turbine_root role can do anything, the only
thing that is required is that user plays the role of
turbine_root. This can be changed and I would actually
like to place permissions for the system (and for turbine
apps in general in a file so that roles/permissions don't
have to be hard coded in the base screens/actions).

> When the list of users (maybe other screens) grows to be
> large, it would be an advantage to add a pager. This could 
> be added in the future when this basic implementation is
> completed (but it should be kept in mind).

Yes, paging has definitely been on my mind. Still
thinking about this one.

> There should be a screen where the current user can update
> (only) his own user details. Possibly when the user logs in
> without the admin role, it could present his user deltails
> screen (like the result of an user find). Currently only the
> users with admin role can use this sample...

That's a good idea. In some cases you might want to let
the user edit some of their own information. Easy enough
to make a template.

> The detail screen could also contain links to the other
> possible actions (like the overview screen). Maybe the 
> delete could be left away at this level. OK, maybe not...it 
> might cause confusion when the admin has updated some 
> parameters and forgets to submit it (trying to continue with
> e.g. roles or permissions).
> 
> It would be good to add a compact description + instructions
> on the bottom of the pages to lead the admin through the
> required steps...

Totally, this is just the first incaration of the app.
It will definitely improve over the next few days and
I will get it into CVS somewhere today as well.

jvz.



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to