You wouldn't by any chance happen to have a link to the guide on gitHub?
I've googled it three times and gone round and round. The closest thing
I find is "Welcome to NVDA to NVDA: NonVisual Developer's Aid to
NonVisual Desktop access" dated 2014.
https://github.com/josephsl/nvda4nvda/blob/master/nvdaarch.md
Is this current?
Thanks,
Tom
On 5/30/2017 6:46 PM, Marlon Brandão de Sousa wrote:
Hey guys,
Be a little bit careful with what you are talking. There is a very
comprehensive tutorial on NVDA scripting written by Joseph Lee on the Internet,
a Google search away from where you are. So do they need to improve
documentation? Yes, they do. Do they have a very high level API like window Il
eyesdid? No, they don't. But stating that they do not have documentation is a
little bit over. In fact, I have just finished Reading One of their tutorials
and it is quite good. It hasn't been always this way but nowadays it is. If you
Google it, you will find two guides. Look for and read the one hosted on
gitHub. Should you be unsure wether what you want can be done, subscribe to the
NVDA devs List and ask for Guidance, they are very very polite there.
Obrigado,
Marlon Brandão de Sousa
Em 30 de mai de 2017, às 17:32, Doug Lee via Scripting
<[email protected]> escreveu:
Speaking as a professional JAWS scripter, I admit I'm surprised to hear you
needed 22 files for what sounds like a simple script. Typically you would have
these:
- A jss file, which compiles to a jsb file, for the code itself. We'll count
that as two. You type your code into the jss file and the JAWS Script Manager
makes the jsb file when you compile it.
- A jsd file for the help text for the scripts. Handled automatically by the
JAWS Script Manager in many cases.
- A jkm file for key mappings. Handled automatically by the Script Manager in
many cases.
You may also include a jcf file for configuration options and/or a jdf file for
dictionary entries, though I doubt your script set for Window-Eyes had the
latter. If you want to name graphic icons, you could use a jgf file.
Frames, though rarely used these days, would involve a jff and a jfd file; but
again, I doubt those would be involved in your project.
I'm still a ways from 22. :-)
On Tue, May 30, 2017 at 04:20:46PM -0400, Tom Kingston via Scripting wrote:
JAWS scripting is a proprietary mish mash of this that the other and his
brother. So there's no such thing as real world resources such as with Python.
I wrote the Window-Eyes script for Reaper and was then surprised to find that
the JAWS script was not locked up. So I downloaded it and took a quick look. I
couldn't believe that what I did in one small VBS file, an XML file, a set
file, and a we file required 22 files to be done in JAWS.
Needless to say, I have no interest in learning a proprietary scripting
method. And I suspect it will probably seem nonsensical to a real programmer's
mind. But that's just speculation. It comes from an experience years ago when
a friend of mine wanted to learn JAWS scripting. Knowing nothing about it I
assumed that at least the common denominators of virtually all programming
languages would apply. Boy was I wrong. My understanding is that it has become
at least somewhat more conventional. But unless all else fails it's not a mess
I wish to drown in.
Regards,
Tom
On 5/30/2017 10:54 AM, Dennis Long via Scripting wrote:
What about scripting for Jaws?
-----Original Message-----
From: Scripting
[mailto:[email protected]] On
Behalf Of Jonathan Cohn via Scripting
Sent: Tuesday, May 30, 2017 10:53 AM
To: Chip Orange; Window-Eyes Scripting List
Subject: Re: migrating apps
Mr Lee of NVAccess / NVDA proposed on twitter yesterday having a one day
class on scripting NVDA. I guess it is time to learn Python. Anybody
interested in doing a set of regular discussions like Chip did way back to
migrate our common knowledge into NVDA scripting knowledge? I wonder how
difficult it would be to have an NVDA that emulates the favorite parts of
WindowEyes. I expect the hardest part considering that NVDA doesn't appear
to have a virtual mode would be the User Windows functions but then it seems
that WindowEyes wasn't supporting that very aggressively.
Best Wishes,
Jonathan Cohn
On Fri, May 26, 2017 at 7:01 PM Chip Orange via Scripting <
[email protected]> wrote:
Hi David,
You could look at the possibility of running your app as a Windows
VBScript rather than a Window-Eyes VBScript. You'd have to do without
the WE dialogs and all the other WE features of scripting which we all
used, but if you don't make use of these features very much, you might
be able to get a Windows VBScript version to run. If you could, this
would be the easiest way to get some apps converted away from WE.
VBScript does have some very basic input and output commands (you can
display a dialog and get a string response from the user), this could
possibly be enough for your needs. It has no equivalents to MSAA or
Windows etc., so nothing which assisted you with accessibility is
likely to run.
Of course, Window-Eyes will continue to run for some indefinite amount
of time ... and I'd be glad to share the source code to Remind Me
Where with anyone who'd like to try tinkering with it while it does.
If you wanted to keep something big like it is running, I would guess
learning VB.net might be the closest to what you're used to.
Like Richard, I feel something like the end of Animal Farm as well.
Take care,
Chip
-----Original Message-----
From: Scripting
[mailto:[email protected]]
On Behalf Of David via Scripting
Sent: Monday, May 15, 2017 11:49 AM
To: Aaron Smith; Window-Eyes Scripting List
Subject: migrating apps
I do understand that an app that has been developed under the great
scripting capability of WineEyes, will not be possible to simply plug
in under Jaws. At least, it is my understanding, that Jaws has its own
dedicated scripting system.
Still, a number of apps, both officially released and many that I have
developed for my personal usage, would be a great miss when migrating.
Whenever the migrating will be. Smile.
Now, is there a way for me, to make my apps become stand-alone, in the
sense that they could be run under any screen reader? That they still
would be using features like the UI capabilities and other
functionality of for instance GWToolkit? I do understand, that apps
that make great usage of, or directly works with internal features of
WinEyes, may not be possible to run under any other screen readers,
since they won't have any functionality to hook on to. But an app like
for instance the "remind me where", that Chip Orange developed, and
which base its main functionality on information from the net, and
greatly on the UI environment of WinEyes scripting, sould such a
program be possible to make go general? Sure I could have thought of a
good number of other apps that I have come to rely on, and which would
have been great to see under other screen readers.
Guess my basic question is, what would I need to do in my app code, to
make it possible to run outside the WinEyes environment, if that is at
all possible? And if realistic, does there exist any sample code that
I can look at, so as to see it done in practicality?
Thanks,
_______________________________________________
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/lis
ts3717
%40comcast.net
<http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/li
sts3717%40comcast.net>
.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/jon
.c.cohn%40gmail.com
.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com/attachme
nts/20170530/13d902d4/attachment.htm>
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/dennisl19
82%40gmail.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/tom.kingston%40charter.net.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/doug.lee%40ssbbartgroup.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
--
Doug Lee, Senior Accessibility Programmer
SSB BART Group (soon to be Level Access)
mailto:[email protected] http://www.ssbbartgroup.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/splyt.lists%40gmail.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
