Billie Walsh wrote:
> Through both these "new YaST" threads I
> have seen a lot of people that aren't happy with where things are. SO,
> they could make their own menus and put things where they want. "YaST"
> is just a container, much like a menu, that opens other
> "applications/modules" to actually do what your trying to do.
I think Billie's right. Allowing users to customise the navigation is a
good idea. Of course, there always needs to be a standard/common way as
well - for administrators to use, to describe in HOW-TOs etc.
There've also been a variety of opinions about whether to have icons,
how many items should be visible, should non-installed items be visible
etc. So it's clear the interface needs to be configurable.
Configurability usually results in extra squirly GUI code, so then I
thought, why not construct the user interface as a web page - the same
way most routers are controlled. Then a lot of display options can be
controlled by CSS and people can rearrange menus and other content to
their heart's desire.
So if I'm configuring say NFS from a YaST web page, what else might I
want to see on that page?:
- breadcrumbs, to show where I am
- links to related items (e.g. DNS config, routing)
- links to related tools (e.g. to ping the NFS server,
or look at it's exports list)
- documentation - either links or javascript controlled blocks or
tooltips etc etc
- an area showing the history of NFS config changes (by the user and/or
automatic system actions)
- an area showing recent relevant log entries
- a personal notes/wiki area so I can record any information I find
useful when I'm doing this task (e.g "use lsof before unmounting" or
a link to a web resource I find useful
<http://www.theregister.co.uk/odds/bofh/>? :)
Cheers, Dave
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
