Re: [orca-list] The Jupiter console screen reader

["B. Henry" <burt1iband gmail com>]

I never got it to work, and for some reason, something I read in docs?, thought it was not only a bit 
complicated to set up, but was also a bit more 
complicated to use than traditional screenreaders. 
Even if the latter is true, it has some of what is sorely lacking in speakup, e.g. the per ap profiles. 
Carl tries hard to make things reliable, so I'm willing to give it another try for sure.
And your friend and I certainly share feelilngs when it comes to how to best use CLI/text-based apps. 
I'd certainly not use some of the programs I use if I could only run them in terminal-emulators. 
Not that I don't fire up something like gnome-terminal, lxterminal, ... one of these regularly, but so far I 
just do not see a substitute for a good 
console screenreader.
Please keep us informed of how your experimentation goes.
Thanks.
   

-- 
     B.H.
   Registerd Linux User 521886


  Kyle wrote:
Mon, May 09, 2016 at 12:37:45PM -0400

> This sounds truly awesome, except for the fact that it still needs a
> kernel module that is not part of the mainline (not staging) kernel. I
> feel it is much better to put a screen reader 100% in userspace,
> because it is far easier to contribute code to any userspace
> application than it is to patch kernel code, and because a crash of a
> userspace application only crashes that application, which can be
> restarted, whereas a crash in a kernel module will usually cause the
> entire kernel to crash, which of course takes the whole OS down with
> it. That said, since Acsint/Jupiter is a standalone module that could
> possibly be built using something like dkms, it may be much more usable
> on more devices, as one should only need the correct Linux headers for
> the version of the kernel installed on the system in order to build the
> needed module, and then the rest is in userspace, so builds
> independently of the kernel. I seem to recall seeing an AUR package for
> this, so I may try to get it running on my Odroids, just to see whether
> or not it can be done, both on 32-bit and 64-bit ARM. Since it is a
> standalone module and doesn't require building an entire kernel, it may
> solve a problem I've been pondering for one of my fellow XU4 users who
> simply can't stand not having a text only console <smiles>.
> Sent from the joy fantastic
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org