Hi, this is tricky.
I've code managing this in event_valueChange, returning or not
depending on the self.increment variable, but it fails when the end
key is pressed. Then sometimes the date field is not correct. It works
well with arrows.
Then for now I'm not convinced with my code.

Cheers

El 01/10/2017 a las 7:44, Abdel escribió:

Hi all,

@Derek:

Yes, what you ask can be done.

However, there can be several ways to do it, some simple and some
more complicated.

@Noelia:

In one of your previous emails, you suggest the following:

Anyway, you could try to manage this in event_valueChange()

def event_valueChange(self):
return

I think it's important to keep something in the event_gainFocus of
the overlayClass, it already contains the call of the function that
gives the user the label of the current field when moving to the date
dialog window.

Thanks.

Cheers,
Abdel.

Le 01/10/2017 à 05:22, derek riemer a écrit :

Can you guys improve the accessibility with dynamic annotation >
instead? > > On Sat, Sep 30, 2017 at 8:14 AM, Noelia Ruiz

<nrm1977@gmail.com > <mailto:nrm1977@gmail.com>> wrote: > > Hi Abdel,
I think that the correct way to do this is using >
speech.cancelSpeech(). If I deactivate the speech mode while in the >
dialog and the press right arrow, speech mode is turned to talk. >
Anyway, if I was you, since the user can choose if wants or not to >
improve the accessibility of the dialog, and consequently make the >
calculation, I simply would use ui.message. Really a user could turn

off speech and braille for testing, to check how the speech viewer
works. Then I think we shouldn't suppose that braille is on if

speech > mode is off. Also, would you like me to send a PR to explain
my ideas > in practice instead of doing it with my words? Just if you
prefer. > > > Cheers > > > El 30/09/2017 a las 15:47, Abdel escribió:

Hi Cyrille, > > You're right. There was indeed a problem with

this constant declared > at the head of the module. > > I added it as
an attribute of the overlay class used by the add-on to > manage the
labels of the date fields, and it works well now. > > Noelia, your
suggestion to apply the overlay class if the key of the >
configuration file to report label is set to True is very good, I >
also added it. > > Tell me if everything is better. > > I even added
a condition for Braille users who work without speech in > the
function of announcing labels. > > The download link is the same: >
>
https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon
>
<https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon>
> > > Thanks again for your suggestions and feedbacks.

> Cheers, Abdel. > > > Le 30/09/2017 à 07:02, Noelia Ruiz a écrit :

Hi, I agree: it doesn't work correctly. I suppose that >
speech.cancelSpeech() didn't work well in this case. I think this is

tricky to fix properly. Anyway, you could try to manage this in >

event_valueChange() > > def event_valueChange(self): return > > And
then try to call super(MyDayOfWeek, self).event_valueChange() in >
the scripts you want that value is reported, for instance, arrow keys

and so on. > > Also, I would try to make this custom class is used

when the add-on > configuration is set to report the field types. > >
Cheers > > El 29/09/2017 a las 23:01, Cyrille via Groups.Io escribió:

Hi Abdel > > The speech OFF fix does not work correctly. Indeed,

as soon as I move > with left/right arrows, the speech turns back.
This can be easily > tested by deactivating speech with NVDA+S just
before moving with > left or right arrows. You should define
savedSpeechMode just before > testing it with the if statement, not
at the beginning of the > module. > > Cheers. > > Cyrille > > > > >
-----Message d'origine----- De : nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> >
[mailto:nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io>] De la part de Noelia >
Ruiz Envoyé : vendredi 29 septembre 2017 20:11 À : >
nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> Objet : Re: [nvda-addons]

dayOfTheWeek-3.0-dev #AddonTesting > > OK, tomorrow I will perform

a new review. Also, as always, I > encourage you and other people to
review add-ons too. I will send > another post with two of my add-ons
not reviewed. Of course, it's not > mandatory; I performs reviews
regardless on this. It's just a way to > recall that there are
developed add-ons not reviewed, and maybe a > chance to practice this
ability and, if someone is interested, to > post on the website. I
use one of them, the other was created for > comments on the spanish
list and I don't use it. > > Cheers > > El 29/09/2017 a las 19:44,
Abdel escribió: > > Hi Noelia and all, > > As agreed, here is the
latest version 3.0-dev of the dayOfTheWeek > add-on. > > The changes
are summarized in the readme.md <http://readme.md> of the > repo. > >
These changes include: > > 1. Back to the %A format for the day of
the week because it allows > to recognize a greater number of
languages. > > 2. Improved the accessibility of the date selection
with recognition > of the 3 fields 'Day', 'Month' and 'Year'. > > 3.
Added a technique for the integration of the Georgian language > for
the recognition of the days of the week. > > 4. Added a
configuration dialog box to enable or disable the > announces of the
labels. > > 5. Moved the add-on submenu from "Tools" to
"Preferences". > > 6. Changed the add-on category to "Day of the
week". > > Download link: > >
https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon
>
<https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon>
> > > > Repo page:

> https://github.com/abdel792/dayOfTheWeek/ >

<https://github.com/abdel792/dayOfTheWeek/> > > Noelia, I have taken
your comments into account for the speechMode, > I added the
verification of its state before putting it on off. > > If you have
any other comments, they are welcome. > > You can do a new review if
you want. > > Users, your feeddbacks are also welcome. > > Thanks. >

Cheers, Abdel. > > > Le 28/09/2017 à 21:40, Cyrille via Groups.Io a

écrit : > > Hi Abdel and all > > OK. Sorry for my previous message
about translation, I do not always > read all the list's messages and
thus I am not yet used to the > add-on release process. > > Cheers >

Cyrille > > > -----Message d'origine----- De :

nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> >
[mailto:nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io>] De la part de Abdel >
Envoyé : mercredi 27 septembre 2017 23:19 À : >
nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> Objet : Re: [nvda-addons]

dayOfTheWeek-3.0-dev #AddonTesting > > Hi Cyrille, > > I know you,

you're my friend lol! > > The French translation of the add-on should
be done as soon as the > add-on will be declared stable by the
reviewers and users. > > Thank you for your test and comment. > >
Cheers, Abdel. > > > Le 27/09/2017 à 22:41, Cyrille via Groups.Io a
écrit : > > Hello Abdel > > I am using NVDA in french. When moving
with left or right arrow in > the date fields, the messages are heard
in english and not translated > in french. Could you fix it ? The
message says: "You can select a > day/month/year with the vertical
arrows" Everything else is OK. > Cheers. > > Cyrille > > -----Message
d'origine----- De : nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> >
[mailto:nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io>] De la part de Abdel >
Envoyé : mercredi 27 septembre 2017 21:48 À : >
nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> Objet : Re: [nvda-addons]

dayOfTheWeek-3.0-dev #AddonTesting > > Hi, > > As agreed, I just

updated the dayOfTheWeek add-on by correcting the > following bugs: >

1. Fixed the encoding errors by removing .decode('mbcs'). > > 2.

Fixed the recognition of the date fields. > > The download link is
the same: > >
https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon
>
<https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon>
> > > > Your reviews and feeddbacks are welcome.

> Enjoy. > > Cheers, Abdel. > > > > Le 27/09/2017 à 08:05, Abdel a

écrit : > > Hi, > > Thanks. > > For the encoding problem, it is
simple to fix. > > For the recognition of the date fields, if you
don't type a date, it > works well. > > However, if you enter a date,
the fields are not correctly > recognized. > > I think of the
following solution: > > 1. Store the current date in a variable. > >
2. Stop the speech. > > 3. Simulate pressing a key, in this case, the
vertical arrows. > > 4. Store the reached date in a variable. > > 5.
Compare the 2 variables and determine the current field. > > 6.
Return to the first date and reactivate speech. > > I'm working on it
for the moment. > > I'll keep you informed. > > Thanks again for your
feedbacks. > > Cheers, Abdel. > > > Le 27/09/2017 à 05:34, Noelia
Ruiz a écrit : > > Hi, my log is similar when the error happens. > >
Cheers > > El 27/09/2017 a las 2:04, وفيق طاهر escribió: > > error:
ExtensionGlobalPlugin version 6.5 INFO - core.main > (01:58:09.545):
NVDA initialized ERROR - unhandled exception > (01:58:24.108):
Traceback (most recent call last): File >
"C:\Users\wafiq\AppData\Roaming\nvda\addons\dayOfTheWeek\globalPlugins\DayOfTheWeek.py",
> > > line 78, in onOk

File "encodings\mbcs.pyc", line 21, in decode UnicodeEncodeError: >
'ascii' codec can't encode characters in position 0-7: ordinal not

in > range(128) INFO - >
globalCommands.GlobalCommands.script_navigatorObject_devInfo >
(01:58:26.615): Developer info for navigator object: name: >
u'\u0645\u0648\u0627\u0641\u0642' role: ROLE_BUTTON > > 2017-09-27
0:44 جرينتش+02:00, David Moore <jesusloves1966@gmail.com >
<mailto:jesusloves1966@gmail.com>>: > > Thanks a lot! I will give
this a whirl! David Moore Sent from Mail > for Windows 10 > > From:
Abdel Sent: Tuesday, September 26, 2017 3:04 PM To: >
nvda-addons@nvda-addons.groups.io >
<mailto:nvda-addons@nvda-addons.groups.io> Subject: Re: [nvda-addons]

dayOfTheWeek-3.0-dev #AddonTesting > > Hi, > > As announced, here

is the download link of the add-on > dayOfTheWeek-3.0-dev: > >
https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon
>
<https://github.com/abdel792/dayOfTheWeek/releases/download/v3.0-dev/dayOfTheWeek-3.0-dev.nvda-addon>
> > > > > This version adds the following improvements:

> 1. Back to the %A format for the day of the week because it allows >

to recognize a greater number of languages. 2. Improved the >
accessibility of the date selection with recognition of the 3 fields

'Day', 'Month' and 'Year'. > > I'll update the readme on the

website when this become stable. > > If no feedbacks or bugs are
notified, this could be in twoo weeks. > > You can found the
documentation here: > > https://github.com/abdel792/dayOfTheWeek >
<https://github.com/abdel792/dayOfTheWeek> > > If you want to review
the diffs in code, please see: > >
https://github.com/abdel792/dayOfTheWeek/compare/3a4ec00d6a71...becdc69fd5de
>
<https://github.com/abdel792/dayOfTheWeek/compare/3a4ec00d6a71...becdc69fd5de>
> > > > > Thanks.

> Cheers > > > Le 26/09/2017 à 17:22, Abdel a écrit : > > Hello

everyone, > > I would like to announce the future release of
dayOfTheWeek-3.0. > > After a long reflection, I decided the
following: > > 1. The format %A' for the day of the week is probably
the best > format. > > Why? > > According to the description of this
format, the day of the week > would automatically be in the language
of the system, so it is an > advantage: > > %A Weekday as locale’s
full name. > > http://strftime.org/ > > The %w format gives the day
in a decimal number from 0 to 6, it's > requires the languages
available in NVDA, but unfortunately, the > locale name yo_NG for the
Nigerian is not present, while the %A > format recognizes it well. >

I think it would be more interesting to keep the %A format during a
period of experimentation. > > For the Georgian, just add a

date.Format ('%A').decode ('mbcs') and > the day should be displayed
correctly for all available languages. > > 2. I propose the
following, for the accessibility of the fields > "day", "month" and
"year" in the wx.DatePickerCtrl. > > When the focus is on the date
displayed by the datePicker, you are > automatically notified if you
are on the field "day", "month" or > "year". > > When you move with
the horizontal arrows, in the datePicker, you are > also notified
immediately on what field you are. > > You can therefore choose
another value with the vertical arrows, > while knowing what field it
is. > > The DatePickerCtrl is also available in wx 4.0 under the name

wx.adv.DatePickerCtrl, so I think we should be able to use it >

without problems with Python 3. > >
https://docs.wxpython.org/wx.adv.DatePickerCtrl.html >
<https://docs.wxpython.org/wx.adv.DatePickerCtrl.html> > > I'll
announce this development version of the dayOfTheWeek add-on in > a
next email, with its download link. > > Cheers, Abdel. > > > > > > >

> > > --- L'absence de virus dans ce courrier

électronique a été vérifiée > par le logiciel antivirus Avast.
https://www.avast.com/antivirus > <https://www.avast.com/antivirus> >

> > > > > > > > > > > > > > > > > > > --- L'absence de virus dans

ce courrier électronique a été vérifiée > par le logiciel antivirus
Avast. https://www.avast.com/antivirus >
<https://www.avast.com/antivirus> > > > > > > > > > > > > > > > > >

-- > > Derek Riemer: Improving the world one byte at a time! > >

* University of Colorado Boulder Department of computer science, 4th

year undergraduate student. * Accessibility enthusiast. * Proud

user > of the NVDA screen reader. * Open source enthusiast. * Skier.

Personal website <http://derekriemer.com>

Hi all,

@Dereck:

Yes, what you ask can be done.

However, there can be several ways to do it, some simple and some
more complicated.

@Noelia:

In one of your previous emails, you suggest the following:

Anyway, you could try to manage this in event_valueChange()

def event_valueChange(self):
return

I think it's important to keep something in the event_gainFocus of
the overlayClass, it already contains the call of the function that
gives the user the label of the current field when moving to the date
dialog window.

Thanks.

Cheers,
Abdel.

Some initial observations:

1. Don't include the word "dialog" in the dialog title as it makes
NVDA speak the word twice.
2. Traditionally, the OK button should come before the Cancel button
in the tab order.
3. It would be nice to have a setting which allowed the user to
specify that the dialog should close after a link had been activated.
4. Personally, I'm probably only ever going to use this to extract
links from text and open one of them using my default browser. So I
think it's a bit inefficient to check what browsers I have installed
every time I activate the dialog. I'm not really sure what the
solution to this could be, but some possible thoughts:

A. Have two assignable scripts: one to offer a choice of browser, one
to just present a list of links with an OK button.
B. Show the buttons to open a link in all browsers by default, and
only check whether the particular browser is installed once the user
clicks one of them.
C. Similar to the above, but show a drop-down of browsers instead of
the buttons. At the top of the list of choices would be "Default
Browser", then each browser that the add-on supports. When the user
presses Enter or activates the OK button, check whether the browser is
installed. If not, speak a message. If "Default Browser" is selected
when they press OK, just use webbrowser.open.

Those are just some thoughts for improvement, but I really do like the
add-on. Often, I get sent links to articles with the links embedded
in the middle of the text, e.g. copied tweets, and this makes it
really easy to act on them.

Regards,

James Scholes
https://twitter.com/JamesScholes



.

Hmm, well I like to have a second or a third go at it as many links these days are impenetrable for what they actually are for.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "James Scholes" <james@jls-radio.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Monday, October 02, 2017 3:03 PM
Subject: Re: [nvda-addons] openLinkWith put links in a dialog to be opened with

Brian's Mail list account via Groups.Io wrote:

In the case of not checking the browser mentioned elsewhere, does this cause an issue?

No, but it's a redundant check which involves actively querying the file system. If a user is only ever going to use their default browser, it's unnecessary.

It might be a nice idea to state in the dialogue which browser you think is set as default on the machine in some way.

The add-on uses Windows functionality similar to that used by the Run dialog to open the links, to ensure that even if you have a completely bizarre application registered as the default browser it will still work. In that sense, there should never be a time when the add-on gets it wrong.

I don't want the dialogue to close by default either as I often use this to get every link in a so called newsletter opened in a new tab

Perhaps the dialog could offer a multiselect list or an "Open All" button.

after all esc dismisses it in any case, so where is the hassle?

Don't get me wrong, this isn't a big complaint. Just an initial observation that, more often than not, my personal use case is to open one link. At that point I'd like the dialog to be dismissed so I don't have to do it myself. It's laziness on my part, plain and simple, but laziness that could easily be facilitated by a single boolean setting.
Regards,

James Scholes
https://twitter.com/JamesScholes

Brian's Mail list account via Groups.Io wrote:

In the case of not checking the browser mentioned elsewhere, does this cause an issue?

No, but it's a redundant check which involves actively querying the file system. If a user is only ever going to use their default browser, it's unnecessary.

It might be a nice idea to state in the dialogue which browser you think is set as default on the machine in some way.

The add-on uses Windows functionality similar to that used by the Run dialog to open the links, to ensure that even if you have a completely bizarre application registered as the default browser it will still work. In that sense, there should never be a time when the add-on gets it wrong.

I don't want the dialogue to close by default either as I often use this to get every link in a so called newsletter opened in a new tab

Perhaps the dialog could offer a multiselect list or an "Open All" button.

after all esc dismisses it in any case, so where is the hassle?

Don't get me wrong, this isn't a big complaint. Just an initial observation that, more often than not, my personal use case is to open one link. At that point I'd like the dialog to be dismissed so I don't have to do it myself. It's laziness on my part, plain and simple, but laziness that could easily be facilitated by a single boolean setting.
Regards,

James Scholes
https://twitter.com/JamesScholes

hello brian and all
Really there was a bug in the regular expression responsible for parsing
the text
and it is now hopefully fixed
the link for the addon is:
https://github.com/ibrahim-s/openLinkWith/releases/download/v1.0/OpenLinkWith-1.0.nvda-addon
you can test it clearly in the readme.md file in nvda addon template folder
select all and press the addon command
you will notice that all urls are cleanly extracted.
thank you
best regards
ibrahim


On 01-Oct-17 5:52 PM, Ibrahim Hamadeh wrote:

hello Brian
yes, sorry for that
I have experienced that also
and really I am trying to review the regular expression used for parsing
the text
hope I can fix it
thank you for your testing and remarks
ibrahim.


On 01-Oct-17 1:10 PM, Brian's Mail list account via Groups.Io wrote:

Hi, could I just say that if you use this on an email from the .io
users list, some of the links append text to the end that makes them
invalid when clicked. Not sure what is going on here myself. but the
links in the email as sent dowork correctly. I was using Outlook
express but suspect any mshtml display might be the same.
Could it be that carriage returns are seen as nothing and then it
moves on to the next space?
Try the donate link.
I also think its missing some links.

Maybe it only works in other text displays but I did select all then
invoked the add on.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Ibrahim Hamadeh"
<ibra.hamadeh@hotmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, September 28, 2017 8:49 PM
Subject: Re: [nvda-addons] openLinkWith put links in a dialog to be
opened with

hello James
In the addon files there is a module named urlfinder.py uses regular
expressions
parses the selected text to get the urls out of it.
the addon then shows the links in a dialog, along with buttons for
browsers found on pc
if pressed on a link in the list, it will be opened with default browser
in the addon I used the webbrowser module, and also subprocess module.
your thoughts for extending the addon are really beautiful
especially adding an edit field that works as address bar
but as you have said let's first stand on a starting point
and if things worked ,we may then move ahead.
thank you for your advice about packaging the addon
and really thank you for all recommendations and thoughts
greetings
ibrahim


On 28-Sep-17 9:14 PM, James Scholes wrote:

It all depends what you're trying to accomplish. I'd suggest that as
a base, you focus on:

1. Parsing links from a piece of text;
2. Showing the links in a dialog;
3. Allowing the user to open one of the links in their default browser.

For that, you should use Python's webbrowser module. It's had years
of testing and it uses the same APIs used by Windows when you type a
URL into the Run dialog. This will create a good user experience
without surprises.

If you then want to extend the add-on's functionality, here are some
ideas:

1. Allow the user to set a specific browser path which will be passed
the URL as a command line argument.
2. Allow the user to create their own regular expressions for parsing
links in the text, e.g. Spotify track links or links to FTP sites.
3. Extend the above by allowing the user to set specific browser paths
for different link types, for example it doesn't make much sense to
open Spotify links in Firefox.

These are just some ideas, and as with any project there are probably
countless others. But I would definitely say that as a starting
point, you should focus on parsing HTTP and HTTPS links out of some
text, and then allowing them to be opened in the user's default
browser. You should also avoid trying to work out which browser that
should be, or limiting your add-on to only work with commonly
installed browsers in common locations. Once that's working, you can
share it, perhaps even get it put up on the NVDA Add-Ons page, and
people will give you feedback on how they're personally using it.

On one final note, if you want people to test your add-ons, please
package them as .nvda-addon files, not RAR archives.

Regards,

James Scholes
https://twitter.com/JamesScholes



.

.

INFO - __main__ (04:25:13.690):
Starting NVDA
INFO - core.main (04:25:14.411):
Config dir: C:\Users\dpy\Downloads\新建文件夹\userConfig
INFO - config.ConfigManager._loadConfig (04:25:14.411):
Loading config: .\userConfig\nvda.ini
INFO - core.main (04:25:14.464):
NVDA version 2017.3
INFO - core.main (04:25:14.464):
Using Windows version 10.0.15063 workstation
INFO - core.main (04:25:14.464):
Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]
INFO - core.main (04:25:14.464):
Using comtypes version 0.6.2
INFO - synthDrivers.espeak.SynthDriver.__init__ (04:25:15.006):
Using eSpeak NG version 1.49.1 dev
INFO - synthDriverHandler.setSynth (04:25:15.420):
Loaded synthDriver espeak
INFO - core.main (04:25:15.420):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (04:25:15.421):
Braille input initialized
INFO - braille.initialize (04:25:15.423):
Using liblouis version 3.2.0
INFO - braille.BrailleHandler.setDisplayByName (04:25:15.423):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (04:25:15.635):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (04:25:15.640):
UIAutomation: IUIAutomation3
INFO - core.main (04:25:16.638):
NVDA initialized
WARNING - characterProcessing.SpeechSymbols.load (04:25:17.177):
Invalid line in file locale\zh\symbols.dic: ﹩ 錢號all
INFO - updateCheck.AutoUpdateChecker._started (04:25:17.213):
Performing automatic update check
INFO - config.ConfigManager.save (04:25:21.736):
Base configuration saved
ERROR - gui.addonGui.AddonsDialog.installAddon (04:25:40.752):
Error opening addon bundle from C:\Users\dpy\Downloads\emoticons-5.7.nvda-addon
Traceback (most recent call last):
  File "gui\addonGui.pyo", line 110, in installAddon
  File "addonHandler.pyo", line 470, in __init__
  File "addonHandler.pyo", line 566, in __init__
  File "configobj.pyo", line 1219, in __init__
  File "configobj.pyo", line 1302, in _load
ConfigObjError: Parsing failed with several errors.
First error at line 1.

hello Brian
yes, sorry for that
I have experienced that also
and really I am trying to review the regular expression used for parsing
the text
hope I can fix it
thank you for your testing and remarks
ibrahim.


On 01-Oct-17 1:10 PM, Brian's Mail list account via Groups.Io wrote:

Hi, could I just say that if you use this on an email from the .io
users list, some of the links append text to the end that makes them
invalid when clicked. Not sure what is going on here myself. but the
links in the email as sent dowork correctly. I was using Outlook
express but suspect any mshtml display might be the same.
Could it be that carriage returns are seen as nothing and then it
moves on to the next space?
Try the donate link.
I also think its missing some links.

Maybe it only works in other text displays but I did select all then
invoked the add on.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Ibrahim Hamadeh"
<ibra.hamadeh@hotmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, September 28, 2017 8:49 PM
Subject: Re: [nvda-addons] openLinkWith put links in a dialog to be
opened with

hello James
In the addon files there is a module named urlfinder.py uses regular
expressions
parses the selected text to get the urls out of it.
the addon then shows the links in a dialog, along with buttons for
browsers found on pc
if pressed on a link in the list, it will be opened with default browser
in the addon I used the webbrowser module, and also subprocess module.
your thoughts for extending the addon are really beautiful
especially adding an edit field that works as address bar
but as you have said let's first stand on a starting point
and if things worked ,we may then move ahead.
thank you for your advice about packaging the addon
and really thank you for all recommendations and thoughts
greetings
ibrahim


On 28-Sep-17 9:14 PM, James Scholes wrote:

It all depends what you're trying to accomplish. I'd suggest that as
a base, you focus on:

1. Parsing links from a piece of text;
2. Showing the links in a dialog;
3. Allowing the user to open one of the links in their default browser.

For that, you should use Python's webbrowser module. It's had years
of testing and it uses the same APIs used by Windows when you type a
URL into the Run dialog. This will create a good user experience
without surprises.

If you then want to extend the add-on's functionality, here are some
ideas:

1. Allow the user to set a specific browser path which will be passed
the URL as a command line argument.
2. Allow the user to create their own regular expressions for parsing
links in the text, e.g. Spotify track links or links to FTP sites.
3. Extend the above by allowing the user to set specific browser paths
for different link types, for example it doesn't make much sense to
open Spotify links in Firefox.

These are just some ideas, and as with any project there are probably
countless others. But I would definitely say that as a starting
point, you should focus on parsing HTTP and HTTPS links out of some
text, and then allowing them to be opened in the user's default
browser. You should also avoid trying to work out which browser that
should be, or limiting your add-on to only work with commonly
installed browsers in common locations. Once that's working, you can
share it, perhaps even get it put up on the NVDA Add-Ons page, and
people will give you feedback on how they're personally using it.

On one final note, if you want people to test your add-ons, please
package them as .nvda-addon files, not RAR archives.

Regards,

James Scholes
https://twitter.com/JamesScholes



.

.

----- Original Message -----

From: Florian Ionașcu

To: nvda-addons@nvda-addons.groups.io

Sent: Sunday, October 1, 2017 11:56 AM

Subject: [nvda-addons] An add-on that makes NVDA to read automaticaly the subthreaders of YouTube Video when pressing a hotkey. #addonrequest

Hello everyone!

I come with a suggestion from a member of the Romanian community. As the topic says, he wants an add-on that makes NVDA to read automaticaly the subtthreaders of the youTube videos when pressing a hotkey. Before posting this suggestion here, I asked all members of the Romanian community about that and the majority gave me positive feedback.

Cheers,

Florian

Sure, but my idea was that you add 80, for instance, if the limit of the
line is 85.
In this way you get a similar result.

Cheers

El 01/10/2017 a las 19:20, Mohammadreza Rashad escribió:

Sorry, but I mean a feature like that exists on typewriters could be
added.
I set the maximum line to 80 characters. When I reached the character
74 or 75, the add-on could notify me by another beep.

۱۳۹۶-۰۷-۰۹ ۱۹:۲۰ +۰۳:۳۰ گرینویچ, Noelia Ruiz <nrm1977@gmail.com>:

Hello, it's configurable: You can set the lengh of line, for instance,
80 characters, to listen a hight tone, and if you want or not to hear
another low tone when the start of the next line is reached.
Cheers

El 01/10/2017 a las 17:47, Mohammadreza Rashad escribió:

Hello dear Noelia,
CursorLocater is an interesting add-on. It would be more functional if
a user could set an indicator before the cursor reaches the end of
line; e.g. 5 or 6 characters before final limit, it beeps using a
different tone.
Of course, it is just an idea.
Thanks of your great add-ons and excuse me because of my bad English.

۱۳۹۶-۰۷-۰۷ ۲۲:۲۴ +۰۳:۳۰ گرینویچ, Noelia Ruiz <nrm1977@gmail.com>:

Hi, these add-ons aren't reviewed for now. If you are interested,
here's
info about them

cursorLocator: NVDA add-on to know the caret position respect to the
start of the current line.
Someone asked about this on the spanish mailing list:

https://es.groups.yahoo.com/neo/groups/nvdaespanol/conversations/topics/28978;_ylc=X3oDMTM3bmxidWZkBF9TAzk3NDkwNDYzBGdycElkAzU1MTg2NzQxBGdycHNwSWQDMTY2MDM5NjA5NQRtc2dJZAMyOTAxMgRzZWMDZnRyBHNsawN2dHBjBHN0aW1lAzE0OTY5NDE5NDkEdHBjSWQDMjg5Nzg-

Repo:

https://github.com/nvdaes/cursorLocator



- vitalSourceBookshelf: I use this program and the add-on to read and
save ePUB in its library. I also opened an issue and a PR in NVDA, not
closed nor merged. The evaluation tests have changed since I created
the
issue, but for me this program is comfortable with the add-on:

Issue with info:
https://github.com/nvaccess/nvda/issues/7155

Repo:

https://github.com/nvdaes/vitalSourceBookshelf

If you have never reviewed an add-on, you may want to start with the
second one.

Cheers