Bryen wrote:
On Sat, 2007-11-24 at 17:59 -0600, Billie Walsh wrote:
Kevin Dupuy wrote:
On Nov 24, 2007, at 6:51 AM, Billie Walsh wrote:
Thomas Goettlicher wrote:
Hi everyone,
we want to redesign the YaST Control Center. Therefore we are looking
for a radical new design.
I agree with everyone else. It doesn't need a "complete" redesign. A few
tweaks maybe, but not a whole new design. It's functional. It works. And
even a NOOB can figure out what the heck does what. I did with my first
install of SuSE 9.0, AND without asking any mailing list.
I don't know how competent you were with a computer with SUSE 9.0. I
remember using 9.0, and (the QT based YaST, anyway) was exactly the
same. The number of YaST modules has gone up, the things YaST can do
has gone up, and for a new user it can be very confusing!
SuSE 9.0 was the first time I ever worked on anything other than
DOS/Windows. On the other hand I had used about everything from about
DOS 3/Windows 1 up through Win ME then XP. My first PC was an 8088XT. My
first computer was a TI 99/4A then a CoCo.
What the heck is so confusing about "Software" in the left panel and
"Software Management", "Online Update", etc in the right. OR, "Hardware"
in left panel and "TV Card", Mouse", Keyboard", etc in the right.
When you open a module in YaST you get hints in the left panel to what
needs to be put in the right panel. IMHO, these could use a little
touching up but they are there.
It appears to me that just about everything in YaST is pretty much self
explanatory.
Okay... so, as an example, in Yast > Network Services > NIS Server. How
does that become self-explanatory to someone who has never heard of NIS
before?
Where would YOU put NIS server?
And what would you call it that would *NOT* frustrate the
living hell out of people who DO know what an NIS server is,
(and probably looking specifically for "NIS")
If need be, it could be expanded to the full name
"Network Information Server"
The WORST that can happen for someone who doesn't know
what NIS is this -- they open up the module, and then
they either decide to play with it, or they say, "that's
not what I want" and close it.
The only cure for ignorance is education -- once they
know what NIS is, then it's no longer a problem ... and
before they know what NIS is, no amount of handholding
is going to make up for the fact that they are ignorant
(i.e. they LACK the knowledge) of what NIS is.
Even further... Click on Help in the NIS Server module and the
following message comes up:
"Select whether to configure the NIS server as a master or a slave or
not to configure a NIS server."
Again, how is this self-explanatory? That's the point some of us are
trying to make. There should be at least a brief explanation to the
purpose of a module's services.
On that point, you're correct. But that doesn't call
for a major re-write -- it calls for well-written text
to pop up when a user clicks on the HELP button.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
