Re: Misc Mozilla

  • From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Fri, 2 Nov 2007 14:23:26 +0200

Well, I have asked him twice but with a lot of intelligent answers, but no helpful answer.

I couldn't find those hotkeys.


----- Original Message ----- From: <james.homme@xxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, November 02, 2007 1:28 PM
Subject: Re: Misc Mozilla

Jamal just said he learned some of the things you didn't by looking at the
interface. You need to do what you preach.


James D Homme, , Usability Engineering, Highmark Inc.,
james.homme@xxxxxxxxxxxx, 412-544-1810

"Never doubt that a thoughtful group of committed citizens can change the
world.  Indeed, it is the only thing that ever has." -- Margaret Mead

            <orasnita@xxxxxxx                                          To
            om>                       programmingblind@xxxxxxxxxxxxx
            Sent by:                                                   cc
            bounce@freelists.                                     Subject
            org                       Re: Misc Mozilla

            11/02/2007 02:57

            Please respond to

Well, I think I understand now.
I need to "learn" to use Commodo.

I never had a learning period for editors like Notepad, TextPad or editors
I've used in the past, and I don't like to need reading help files in order
just to be able to use an editor.

I think an editor should learn us how to use it by just simply looking at
its interface, and this means following the known standards.
Immediately after installing TextPad, I use to set it to follow Microsoft's
conventions. It would be helpful if Commodo would also allow such a thing.

The most accessible programs are not only those who can be accessed with a
certain version of a certain screen reader, but those who can be accessed
those who's native language is not english, without needing to spend time
for learning new interfaces, and so on, with other words, accessible as
as possible.

Thanks for the help files for Commodo. I hope I will find what I need in


----- Original Message -----
From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, November 02, 2007 4:48 AM
Subject: Misc Mozilla

In case this helps those interested in learning Komodo, I've created a
documentation collection at

It includes all text files I found in the installed directory tree, and
all HTML files combined into a single structured text document.  That
is largely duplicative of a text version of the PDF user guide, but I
included both to make sure I got all possible documentation.  I'm pasting
the feedback.txt file below.

Anyone interested in learning Firefox will find a couple of tutorials in
the archive of miscellaneous software documentation at

A few files on open source development are in the miscellaneous
programming collection at

A reminder that the fruit basket example I did with Mozilla XulRunner is


                               Sending Feedback

We welcome your feedback, suggestions, feature requests and bug reports.

Comments and Feature Requests

If you tried Komodo and you would like to see a certain feature, or you
like to tell us how Komodo met or didn't meet your coding needs, send us
email at Komodo-feedback@xxxxxxxxxxxxxxx

ActiveState Community site

Ask questions, get (or give) advice and share code with other Komodo
users here:

Reporting Bugs

If you have found a bug, we'd like to know about it. First, view our
on-line bug
database and see if your bug has already been reported. If you can't find
issue, you can submit a bug report.

To view our bug database and submit a bug report:

1. Go to our on-line bug database at
   From the Komodo Workspace, go to the Help menu and select Komodo Bug
2. Click View Bugs. You can apply filters and then sort the result by
3. If necessary, click Search and enter a keyword for your bug.
4. If you can't see your bug, click Submit a bug.
5. Complete the on-line form with as much detail as possible. This helps
   identify the problem.
6. Click Submit Bug Report.
   If you make a mistake, click Reset.

Your bug will be assigned an ID and you can monitor the progress of your
bug on
this Web site. We will email you when your bug is resolved.


View the list's information and change your settings at

View the list's information and change your settings at

View the list's information and change your settings at

View the list's information and change your settings at

Other related posts: