Re: [orca-list] text console use
- From: Janina Sajka <janina rednote net>
- To: orca-list gnome org
- Subject: Re: [orca-list] text console use
- Date: Tue, 16 Oct 2018 07:51:46 -0400
Hi, Fernando:
I suspect you might need to be moe precise. WebRTC covers three separate
streams of communication, audio (voice), video, and text.
Doing text and voice with a cli app should be pretty straight forward.
Doing video is probably not so straight forward and reasonably begs the
question: "Why?" The gui environment provides far more native support
for two-way streaming video, so taking video to the cli requires a
compelling rationale, imo. I don't see one.
BTW: I believe the standard you'd want implemented is this one:
https://www.w3.org/TR/webrtc/
I would further note that, while this W3C spec is for a browser, there's
no reason it can't be a single purpose, cli browser instance. Sometimes
on mobile platforms we now calls such applications apps--but that's
another discussion topic.
Janina
Fernando Botelho writes:
I looked for someone who could implement WebRTC on the console but could not
find anybody. I can look for funding again, if someone knows the right
person.
Fernando
On 10/13/2018 07:08 AM, Didier Spaier wrote:
To play Youtube on a Linux console, use mps-youtube.
About webRTC: I never heard of it until today. The home page says that Chrome, Firefox, Opera, Android
and IOS are supported and there is also licode:
https://github.com/lynckia/licode
What we need to integrate it with a text web browser like lynx is developers. Do you volunteer?
Of course a graphical environment is easier to grab. But for those who have the patience to learn, a text
UI is usually as good and usually is more feature comlete, when it exists.
Stupidly old school? Yes I am, and proud of it.
I didn't grew up on Commodore and stuff, because I used a personal personal computer for the first time
in 1978 (yes, 40 years ago) and neither ms-DOS (1980) nor Commodore 64 (1082) existed then.
Still I was able to use the computer, which obviously had a proprietary OS, to translate into French its
BASIC interpreter (key words and error messages), all that in 64 Kb of RAM (yes, kilobytes) and not
having the source code at hand.
O Tempora! O Mores!
Best,
Didier
On 10/13/18 6:56 AM, Jace Kattalakis via orca-list wrote:
You find me a CLI browser that can do webRTC and play Youtube without a graphical environment, and I
may change my tune but I'd argue a graphical environment is easir to grab for everyone unless you're
stupidly old school and grew up on Commodore and DOS stuff.
On 12/10/18 20:13, Didier Spaier wrote:
Funnily I would tend to ask the opposite question: why a blind person would need a graphical
environment?
I know at least one blind Slint users who never use one.
I believe that most things done in a graphical environment can also be done in a console, often with
a better productivity. This stands for blind as well as sighted people.
A few examples: for writing you have a lot of text and code editors like nano, emacs and vim, mutt
for emails, lynx and links for web browsing, mplayer to listen to music, vlc to listen to movies,
crafty to play chess, games like freeswipe or scribble, the list goes on and on.
Actually the first personal computer I used nearly 40 years ago didn't have a graphical environment,
maybe that's why I am used to text mode.
Best,
Didier
On 10/12/18 7:48 PM, Michael Weaver via orca-list wrote:
I don't know if this is the right list to ask on as it is not strictly Orca but it is about text
screenreaders but is text console use still necessary. I am not quite clear on this point. The
reason is that you can use the terminals in gnome, Mate or maybe other desktops like mate-terminal
from an alt F2 run prompt which is why I ask about text consoles, your CTRL ALT F1 to F6 which
don't speak with Orca so need a different screenreader.
Just curious with projects like Fenrir.
_______________________________________________
_______________________________________________
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
_______________________________________________
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
--
Janina Sajka
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]