enCruft


Matthew Thomas's recent blog "When good interfaces go crufty" presented aspects of GUIs that are non-intuitive and should be changed. The goal of this project is to explore a prototype GUI that doesn't suffer from " cruft ".

The first two examples of cruft presented in Matthew's blog are summarized here:

  • Document saving should not require user intervention.
  • Quit and Exit menu choices on a GUI are confusing.
This prototype will explore the consequences of changing these two items in a GUI.

The example code is in Java and uses Swing. It requires at least Java 1.2 and a version of Ant installed for doing builds.

A good comparison of a traditional editor in Java is given in the document: Java & Web Programming.





¤   4037 General Bate Drive    ¤   Nashville, TN 37204    ¤
¤   Phone: (615) 292-6496    ¤   Fax: (615) 386-9243    ¤    info@elucidsoft.net     ¤
This documentation was created by the staff of eLucid Software.  The content of these pages is Copyright © 2002 by eLucid Software, all rights reserved, unless otherwise noted.  Send comments, corrections, and suggestions to the author.