User Experience engineering does not require a GUI or an abandonment of the programming and typesetting approach. It does not require the abandonment of providing detailed features. What it requires is that the language and documentation are clear and that functionality doesn't require time- consuming work arounds. For example, if one is running on a Windows environment, one should not have to install another editor and worry about getting that to work, and the outputs should be easily usable and readable by other programs without having to install other kinds of programs and accessories. It means that everything is made simple and clear for the user. There are users, unlike myself, who have never done any programming. Simplicity and clarity are as important as providing desired features. I am saying this as someone whose software has been incorporated into the Sprint network operations system, the AT&T network, the Silicon Graphics workstations, the Coast Guard communications system and other products. I have seen development projects sink and swim, and I am merely discussing what will "swim" if it is to become highly profitable at some point. If I were saying this at a profit-oriented company no one would disagree, let alone generate a flame war. I have seen multi-million projects go down the drain because the management didn't pay attention to issues such as marketing or the user experience.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
