Bug 478380 – www-client/chromium: Install ChromeVox extension for visually impaired users

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Mike Gilbert 2013-07-27 18:49:49 UTC]

ChromeVox is a Chrome screen reader extension by Google.

http://www.chromevox.com/

William and Chris mentioned in IRC that it would be nice for visually impaired users to have a way to install ChromeVox without having to visit the Chrome Store.

I found these instructions for auto-installing extensions:

https://developer.chrome.com/extensions/external_extensions.html

Using the instructions, I created this JSON file which will cause ChromeVox to be installed when you launch Chromium. It just needs to be placed in /usr/lib/chromium/extensions.

http://dev.gentoo.org/~floppym/chromium/kgejglhpjiefppelpmljglcjbhoiplfn.json

We just need to figure out a good way of deploying this JSON file. A few choices:

1. Create an ebuild for it.
2. Add a use flag for www-client/chromium and install it from there.
3. Have chromium install a bash script to create the JSON file at runtime.

Personally, I prefer the first option.

Any further thoughts, comments, objections?

[Comment 1 William Hubbs 2013-07-27 18:54:36 UTC]

Yes, I think the ebuild would be the best option, under app-accessibility. If you want I'll write one. We would just put the json in ${FILESDIR} and install it.

[Comment 2 Chris Brannon (RETIRED) 2013-07-27 19:12:59 UTC]

I'd vote for the global accessibility use flag, but I do think that the
ebuild is viable.

[Comment 3 William Hubbs 2013-07-27 19:14:55 UTC]

Thinking this over, if the chromium and chrome ebuilds use the global
accessibility use flag to install this json file, that would be the most
automatic way to do this, so that is what I support now as well.

[Comment 4 Brian Dolbec (RETIRED) 2013-07-27 23:58:39 UTC]

For a separate ebuild, there is no need to put it in files/ the one line can be echo'd into the file direct from the ebuild.  Same for a use flag trigger in chromium.  It'll save another inode ;)


My favorites are in order:

USE flag in chromium
ebuild
installer script (python or bash)  (could be easily expanded to install a choice of any popular extensions available)  Then the user can install them if/when they want. rebuilds, not necessary.

[Comment 5 Mike Gilbert 2013-07-31 02:46:14 UTC]

A USE flag (accessibility) on the chromium and google-chrome ebuilds works for me.

phajdan.jr: Do you have any suggestions/objections?

[Comment 6 Paweł Hajdan, Jr. (RETIRED) 2013-07-31 04:28:22 UTC]

(In reply to Mike Gilbert from comment #5)
> A USE flag (accessibility) on the chromium and google-chrome ebuilds works
> for me.
> 
> phajdan.jr: Do you have any suggestions/objections?

Sounds good to me.