Re: Now Getting Braille Output From Gnopernicus

[Irene Ryan <irene ryan Sun COM>]

Luis Villa wrote:
> 
> On Tue, 2003-05-13 at 11:57, Irene Ryan wrote:
> > Hi Bill, Luis,
> >
> > I have just started gathering some information to write a chapter on Gnopernicus
> > for the GNOME Accessibility Guide. The focus of the chapter would be on using
> > Gnopernicus but I can also include the necessary information about how to set it
> > up or at least pointers to where the setup is already documented, if that's the
> > case.
> 
> It seems like there probably needs to be a separate 'build and
> installation' guide for most of GNOME, but for a11y in particular- the
> average user of a11y probably doesn't want to/can't build it themselves,
> but the average tester/developer clearly needs help with it. Seems like
> putting all the documentation in one doc probably ignores that, doesn't
> it?
> 
> Luis
>
I agree. The building/installation of the tool definitely doesn't belong in the
GNOME Accessibility Guide (GAG). I thought you were referring to some
configuration-type checks that you need to do before you can get the tool to
work. I would be happy to include information like that in the GAG. However,
since the information you're talking about is for a tester/developer audience,
it doesn't belong in the GAG.
 
The gnome-doc-list is definitely a good place to look for a volunteer to gather
the build/installation information together. I will continue to concentrate on
the end-user information.

-Irene
 
> > Luis Villa wrote:
> > >
> > > On Tue, 2003-05-13 at 10:49, Bill Haneman wrote:
> > > > John:
> > > >
> > > > I am wondering if you have turned on the "accessibility" support gconf
> > > > key or not.  You may have missed that step, it's been mentioned a few
> > > > times on the list.  I think we need to somehow concatenate all this
> > > > information together once again, a number of people have written short
> > > > HowTo documents but nothing quite brings all the information together
> > > > yet.
> > >
> > > You might want to poke the documentation list
> > > (gnome-doc-list gnome org)- I'd bet someone there would be willing to
> > > help condense and arrange all the information, if someone here can
> > > provide pointers to things that have already been written.
> > >
> > > Luis
> > >
> > > > Before accessibility will work across the desktop, you need to check
> > > > this gconf key:
> > > >
> > > > gconftool-2 --get /apps/desktop/gnome/interface/accessibility
> > > >
> > > > if it's "false", set it to true:
> > > >
> > > > gconftool-2 --type bool --set
> > > > /apps/desktop/gnome/interface/accessibility true
> > > >
> > > > (all one line, my emailer is word-wrapping this command).
> > > >
> > > >
> > > > I hope that this will work for you.  If not, then we need to do some
> > > > more diagnostics on gnopernicus (you can kill gnopernicus and srcore,
> > > > and any gnome-speech drivers, from a console and then run gnopernicus
> > > > manually after GNOME has started, perhaps you will see some useful error
> > > > messages).
> > > >
> > > > I am glad to be of help, thanks for your part in trailblazing!
> > > >
> > > > - Bill
> > > >
> > > >
> > > > On Tue, 2003-05-13 at 15:18, John J. Boyer wrote:
> > > > > Bill,
> > > > >
> > > > > The session-manual file that you gave works great. There is now no call to
> > > > > gnopernicus or srcore in my .xinit file. When i type startx there is a
> > > > > delay of about a minute, then the message "Welcome to Gnopern" appears on
> > > > > my braille display. I had a sighted colleague check the screen. gnome is
> > > > > up. The mouse works. However, the Braille display never changes, no matter
> > > > > what is done with the mouse, the keyboard or the front-panel keys on the
> > > > > display itself.
> > > > >
> > > > > I am thrilled to be able to contribute to the development of this screen
> > > > > reader even as a tester, and maybe i can make some code contributions in
> > > > > the future.
> > > > >
> > > > > John
> > > > >
> > > > >  On 13 May 2003, Bill Haneman wrote:
> > > > >
> > > > > > John:
> > > > > >
> > > > > > As Christopher said, you should not start gnopernicus before starting
> > > > > > GNOME (i.e. gnome-session).
> > > > > >
> > > > > > As far as I know, your ~/.xinitrc file need only contain one line,
> > > > > >
> > > > > > "exec gnome-session"
> > > > > >
> > > > > > in order to start GNOME.  I do not know whether an immediate invocation
> > > > > > of "exec gnopernicus" afterwards would cause a race condition or not;
> > > > > > perhaps a 'sleep' in between would be advisable.  The "gnome-session"
> > > > > > call won't return until you quit GNOME, which is why it needs to be
> > > > > > "exec"'ed instead of just placed in the script.
> > > > > >
> > > > > > There's a GUI in gnome for adding startup programs.  Unfortunately there
> > > > > > isn't a proper command-line or script version of this (yet).  But you
> > > > > > can manually edit the session file:
> > > > > >
> > > > > > 1) create directory ~/.gnome2 if it doesn't exist yet
> > > > > > 2) create file ~/.gnome2/session-manual
> > > > > > 3) contents of session-manual file:
> > > > > >
> > > > > > <blank line>
> > > > > > [Default]
> > > > > > num_clients=1
> > > > > > 0,RestartStyleHint=3
> > > > > > 0,Priority=60
> > > > > > 0,RestartCommand=gnopernicus
> > > > > >
> > > > > >
> > > > > >
> > > > > > I hope that helps.
> > > > > >
> > > > > > Bill
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > Well, at least I am getting something on my Alva 320 display. When I start
> > > > > > > Gnome and Gnopernicus the displaly shows "Welcome to Gnopern". Pressing
> > > > > > > the keys on the front panel of the 320 has no effict. Brltty continues to
> > > > > > > work with the Braille Lite 40 in port 1. I can read on the screen that
> > > > > > > that Braille initialization was successful.
> > > > > > >
> > > > > > > In my .xinitrc file I have srcore -p2 just before      exec
> > > > > > > $GARNOME/bin/gnome-session . When I tried replacing "srcore -p2: with just
> > > > > > > "gnopernicus" it appeared to crash the system. I had to reboot - for the
> > > > > > > first time in two months. Moreover, I had to press reset to do it.
> > > > > > >
> > > > > > > I hope these results will help with debugging. They are encouraging, and
> > > > > > > I'm ready to do further testing as soon as I or someone figures out the
> > > > > > > next step.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Computers to Help People, Inc.
> > > > > > > http://www.chpi.org
> > > > > > > 825 East Johnson; Madison, WI 53703
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > gnome-accessibility-list mailing list
> > > > > > > gnome-accessibility-list gnome org
> > > > > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > gnome-accessibility-list mailing list
> > > > > > gnome-accessibility-list gnome org
> > > > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > > > > >
> > > > >
> > > > > --
> > > > > Computers to Help People, Inc.
> > > > > http://www.chpi.org
> > > > > 825 East Johnson; Madison, WI 53703
> > > > >
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > gnome-accessibility-list mailing list
> > > > gnome-accessibility-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > > >
> > >
> > > _______________________________________________
> > > gnome-accessibility-list mailing list
> > > gnome-accessibility-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> >
> 
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list