New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Braille driver for Eco display #4078
Comments
Attachment ecoBrailleAddon-1.0.nvda-addon added by jjimenez0 on 2014-04-16 05:48 |
Comment 1 by jjimenez0 on 2014-04-16 05:53 In ONCE (National Organization of Spanish blind) we have developed a little addon that allow us to use the Eco Braille display with NVDA.
|
Comment 2 by norrumar on 2014-04-21 11:35 Thanks a lot. |
Comment 4 by jjimenez0 on 2014-04-21 12:23 Hi Thanks in advance |
Comment 5 by norrumar on 2014-04-21 13:05 |
Comment 6 by norrumar on 2014-04-21 15:25
|
Comment 7 by jteh on 2014-04-21 21:43 |
Comment 8 by jteh on 2014-04-21 22:12 A few general questions:
For the most part, the code looks pretty good. In addition to comment:6, here is some code review:
I assume this was debugging code that was accidentally left. It should be removed.
Rather than multiple equality checks, use the in operator; e.g.
Unless I'm missing something, you can rewrite this as an elif and get rid of one indentation level. You can also get rid of the parentheses.
Any translatable strings need a translators comment above them. This will do:
Does the display support pressing multiple keys at once? This doesn't seem to be supported by the driver. It's fine if you don't see a need to implement this. I mention it because most drivers do. There is also some extraneous whitespace, but I can remove that easily enough. Thanks again! |
Comment 9 by jjimenez0 (in reply to comment 6) on 2014-04-22 06:26 Yes, of course I want to work in the public repo. It will be the best for all. |
Comment 10 by jjimenez0 on 2014-04-22 06:55
|
Comment 11 by jteh (in reply to comment 10) on 2014-04-22 07:11
This is fine. Keep using the dll for now if you're already using it elsewhere. At least it's a very small dll. |
Comment 12 by norrumar on 2014-04-22 09:04
|
Comment 13 by jjimenez0 on 2014-04-22 09:52 |
Comment 14 by jteh on 2014-04-22 09:55 |
Comment 15 by jjimenez0 on 2014-04-22 09:57
Changes work fine for me |
Attachment EcoBraille.dll added by jjimenez0 on 2014-04-22 09:58 |
Comment 16 by jjimenez0 on 2014-04-22 10:00 |
Attachment ecoBrailleAddon-1.1.nvda-addon added by jjimenez0 on 2014-04-24 06:12 |
Comment 17 by jjimenez0 on 2014-04-24 06:14 |
Comment 18 by norrumar (in reply to comment 17) on 2014-04-24 17:35
Hi, I can't review my modifications: key assignment and deletion of extra spaces.
If you need it, I can create a branch for this ticket in NVDA addon team, and send commit notifications to a mailing list. It's more difficult to work on binary add-ons. I have my personal computer now and can do it if needed. |
Comment 19 by norrumar on 2014-04-28 17:47 |
Comment 20 by nvdakor on 2014-04-28 21:04
|
Comment 21 by jteh on 2014-05-01 07:16 Please include a User Guide section for this similar to those for other displays. The What's New entry shouldn't be added to the branch; that will be committed once it goes to master. Btw, this is the purpose of the "Changes document entry" field in tickets. Thanks. |
Comment 22 by norrumar (in reply to comment 21) on 2014-05-01 09:10
I have changed the comment about braille buttons. I have added try... except to handle a possible exception in EB_Init function when the display is disconnect. Thanks for including this driver into NVDA. My job is now happy and better without switching to JAWS just to use Ecobraille. |
Comment 23 by jteh (in reply to comment 22) on 2014-05-01 10:10
I don't follow. If the display is disconnected, the constructor should fail, so the exception should pass through so NVDA knows the display failed to initialise. We can't do this for BRLTTY, but it should be done for all other displays. |
Comment 24 by norrumar (in reply to comment 23) on 2014-05-01 10:21
OK. It's reverted now. I was testing this driver (in the add-on), loading it, disconnecting the display and restarting NVDA, connecting, etc. I thought that the information shown in the log file was not needed. But your comment is right for me. |
Comment 25 by norrumar on 2014-06-09 16:22 |
Comment 26 by norrumar on 2014-08-05 06:27 |
Comment 27 by jjimenez0 on 2014-12-11 10:47 Hi all, |
Comment 28 by norrumar (in reply to comment 27) on 2014-12-11 11:09
! |
Comment 60 by norrumar (in reply to comment 59) on 2015-05-01 09:40
I have updated the documentation noticing that Ecoplus must be connected before starting NVDA.
Some questions:
|
Comment 61 by jjimenez0 on 2015-05-01 10:15
I don't care which one we select. Both has a good side and a bad side. Right now is only change a line in the source code. And ok for the encoding and the copyright date ( I hope we must not change it to 2014-2016, (smile)) |
Comment 62 by nvdakor on 2015-05-01 10:38 |
Comment 63 by norrumar (in reply to comment 62) on 2015-05-01 10:51
Hi, I agree with you and finally I reverted the modification used in my job. BTW, one time (just one), NVDA gets restarted and a dump was produced in my job, but I think it doesn't is related to Eco display. In the log appears something about braille update, but I didn't report it because it just happened one time. |
Comment 64 by jjimenez0 on 2015-05-01 11:30 |
Comment 65 by jteh on 2015-05-01 11:48 Personally, if there's really no command you can send to these displays to force them to re-initialise/identify themselves, I'd go with the option adopted for other screen readers. It's ugly, but it's probably the better of the two evils. |
Comment 66 by norrumar (in reply to comment 65) on 2015-05-01 12:02
If sequrity reasons don't hold, I think it's better adopt the other option as in other screen readers in order to restart NVDA without problems. |
Comment 67 by norrumar (in reply to comment 66) on 2015-05-01 12:41
Done. I will test this the next Monday in my job, placing the driver into the add-on. I assume ther won't be differences in the results obtained with the add-on and placing the driver into NVDA core. |
Comment 68 by norrumar on 2015-05-02 07:03 Routing keys are described, but I think that not named consistently, so I have writen Route in NVDA user guide, as in the driver with capital R, since key names are capitalized in Ecoplus documentation. |
Comment 69 by norrumar on 2015-05-04 10:15 |
Comment 70 by jjimenez0 on 2015-05-11 11:00
This file and the changes of the files changes.t2t and userGuide.t2t are in the branch t4078 |
Attachment ecoBraille.py added by jjimenez0 on 2015-05-11 11:00 |
Comment 71 by jteh on 2015-06-26 07:22
|
Comment 72 by James Teh <jamie@... on 2015-06-26 07:34
Changes:
|
Comment 73 by jteh on 2015-06-26 07:36 |
Comment 74 by norrumar (in reply to comment 73) on 2015-06-26 09:26
Thank you! Juan Ramón Jiménez (ONCE-CIDAT) is not included in contributors.txt on t4078 branch. I think this could be included later. |
Comment 75 by norrumar on 2015-06-26 13:49 |
Comment 76 by jteh on 2015-06-28 23:11 |
Comment 77 by norrumar (in reply to comment 76) on 2015-06-29 02:08
Hi, I agree with you. He works with other people in CIDAT (a technical center from ONCE, a spanish organization for blind people). |
Comment 78 by jjimenez0 on 2015-06-30 06:44 Hi, sorry for the delay. |
Comment 79 by James Teh <jamie@... on 2015-07-10 04:26
Changes:
|
…aille Plus braille displays. Authors: ONCE-CIDAT <cidat.id@once.es>, Noelia Ruiz Martínez <nrm1977@gmail.com> Fixes #4078.
Reported by jjimenez0 on 2014-04-16 05:47
EcoBraille display are very common in Spain but it doesn’t work with 64 bits systems, so they were falling obsolete.
An addon for Eco Braille display would be very important in order to get working those displays in NVDA even in 64 bits operating systems.
The text was updated successfully, but these errors were encountered: