Yolanda, Or, Guys,
I've been watching this thread with great interest,
wondering what, if anything, I would be able to
contribute.
A GUI that simplifies without obscuring, and which
doesn't break, is kind of a Holy Grail (for me,
anyway).
To make a GUI actually useful from a progamming
point of view, it has to have an API. Anything else
is just a shell.
I think the key will lie in the deliberate clarity
of exposing the API. Document everything, hide
nothing. There will probably never be a perfect
marriage between application programmers and the
writers of OSes and APIs, because there is a
literacy barrier: writers of APIs have to express
*accurately* what it does, and app programmers must
*understand* what that means and how to use it.
Buggy API code is not compulsory. Buggy app code
likewise. But if the API coder keeps secrets the
result will be errors in the apps that make both
the app and the OS/GUI look bad.
Clarity. Openness. Completeness. And if, on top
of that, the thing is actually *well written* you'll
have a minor miracle.
~~Garry
--------------------
> >But, the thing is NOT the interface but how it works (or in this case
> >actually DOESN'T work). I can understand why most users would like a GUI
> >but do they really want one that crashes often?
> >
> >//Bernie
>
>
> The thing is, to create a universal OS with a GUI that is extremely simple
> to use and intuitive, that can be installed and run on almost any hardware
> platform, it's a tough row to hoe. ...
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
