[ludo:]
| http://wikis.sun.com/display/WebStack/Home
| This is what I call V0.0.1 and I need now active feedback from this
| webstack SAMP community to see what we can do for the future SXDE builds
| to have a nice developer experience.
Some comments:
User Entry
----------
Since admin is probably different from the user being added,
'User Name' may be better than 'Your Name' in create user.
For a developer, (ie us :) .) the important part is to add a user and be
done with it, with general interest in
1) shell
2) home dir
3) which *all* groups you want the user to be.
The advanced is really the privileges that you want to assign to that
particular user
The personal data, while very important from an administration point of
view is not very urgent for a developer. so they can be moved to a last
tab 'Personal Information' or 'Optional'
It would be nice if the user can stop entering these details in the
middle, go back and check another user's details and do the same in the
current (-- non modal entry spaces.)
a nice feature will be the ability to clone an existing user.
(think of postgress user, mysql user and apache user - these are the
kinds of users a developer is most likely to add)
on the selection of group box, it will be nicer to use an auto-completing
combo rather than an expanding static list. (You can even take the user
to create group page when he clicks OK if a non-preexisting group is
used.)
Privileges, Services:
-----------
It would be nice if it is possible to dynamically filter the things in
these lists. While the check boxes look nice, it becomes very unwieldy
when you have a lot of entries (even the examples have so many entries
as to make it unwieldy.) Perhaps multi select with two list boxes as we
have in webserver admin is a better idea.
Since we are targeting developers, It might be nice to have a way to
show all the commands that are going to get executed (like Microsoft VC
does for compilation in their property pages). This will help them to
automate these entries in the future (as developers usually do)
Perhaps we also need to think how NIS fits in. (where is the user
defined? in the local system or the NIS -- listing the users in local
system, and creating the user in local system is fast but the same in
NIS is slow, so it may stand to reason to separate them.)
Zones:
-------
Can a user log into a zone directly from the welcome screen? It will
be nice if that is possible. Also it may be useful to add zone option to
the user entry page, so that user is able to do things in multiple
zones with a single change.
Services:
--------
Will the described services design (I cant find it in vpdesign.pdf)
allow us to tie together multiple services? if not:
Can we add some way to group certain services together? ie, for
moodle to work, you need to have both mysql and apache running. it will
be nicer to see start moodle than each different servers starting.
It may also help to allow users of these services ability to invoke
their own front end from our services tab. ie: I usually want to check
the error logs of apache, and mysql. If they there is a way to access
them from the services tab, it will be great.
Diff:
----------
Can we have a place where, we can see a summary of all the things
that have been done
1) since install
2) from a pre-defined checkpoint
3) In this session
or at least some of the above?
It will also help if scripts are provided for each of the above so that
I can run that in a newly installed system and be reasonably sure that
the new system looks like this one.
I realize these things will complicate the UI somewhat, but if we are
aiming the developers, these are the things that (as a dev) I find we do
repeatedly.
(And a plea, can we do something on the console too? like a curses
front-end? - I find doing things on X over a network really painful, or
atleast an HTTP front-end like webmin?)
