Orca Flag Day.

[Rich Burridge <Rich Burridge Sun COM>]

If you are checking out the latest Orca from CVS HEAD, then I've just
checked in some changes that will affect you, and you will need to
re-run orca-setup before you re-run orca.

These changes are listed below. The main reasons for doing them are:

* Prepare for better key echo which will be (hopefully) coming in the
 next week or so. Note that currently the "echo by word" and "echo by
 character" functionality is not fully implemented.

* Make it easier to automatically create the infrastructure to allow
 users to just put their own Orca application scripts under their
 .orca directory (under ~/.orca/orca-scripts/ to be exact), should they so
 desire.

* Allow users to have their own custom Orca Python code, that won't get
 destroyed if you re-run orca-setup (such as Javier's recent sayTime()
 routine). You should now put this code in a file called
 "orca-customizations.py" under your ~/.orca directory.

* Setup the display of the visual braille monitor (useful to sighted people
  to see what would be happening on the braille display - if present).

Please let me know if you find any problems with these changes.

Thanks.

--

       * src/orca/orca-setup.in
         Several changes to the orca-setup script:
         - Removed the "Use key echo?" question and associated
           orca.settings.USE_KEY_ECHO setting.
         - Replaced it with:
           "Echo by word, character, both or none?  Enter w, c, b or n: "
           which  will set two settings to True or False:
             orca.settings.USE_ECHO_BY_WORD
             orca.settings.USE_ECHO_BY_CHAR
           depending upon the users answer.
         - Added in another question: "Use Braille Monitor?  Enter y or 
n: ".
           The Braille Monitor is a visual representation of what is being
           brailled by Orca.
         - Automatically create a "orca-scripts" directory under the
           users .orca directory, if it doesn't already exist.
         - Automatically create an empty __init__.py file in the
           orca-scripts directory, if it doesn't already exist.
           This will enable the user to put their own specific
           applications scripts in the orca-scripts directory,
           and Orca will pick them up.
         - Added a section of code that will generate the following lines
           at the end of the user's user-settings.py file:

             try:
                 __import__("orca-customizations")
             except ImportError:
                 pass

           What this means is that Orca will now look for a file
           called "orca-customizations.py" in the user's .orca directory.
           This file should contain any custom Orca Python code that the
           user wants. Having it in a separate file from user-settings.py
           means it won't get blown away when you rerun orca-setup