I decided to open a new thread, even if it closely ties in with our
previous discussion of migrating scripts from the Wineyes environment.
I want to share with you all, one possible solution for creating
scripts, with a pleasant GUI. At least, from browsing through the
following website, it seems much of the sizing and other control-related
creation will be possible to perform, relying on automated calculations
from the interpretter (or programming environment). I have not yet had
the time and resources to check this out with any real world activity,
but judging from the sample code provided on the linked page, it should
be a relatively easy go, to compose at least the more basic user
interfaces. The programming environment is autoHotkey. I have not
checked too much on other environments - like Python - as of yet, if any
of them have similarly easy UI creation methods. But at least, this
might be one alternative, to let your WinEyes apps go general. Check it
all out on:
https://autohotkey.com/docs/commands/Gui.htmr
If anyone finds this useful, and are willing to share their first simple
codings under this environment, I am sure many of the members on the
list will enjoy to see your project. That way, maybe more developers
will be encouraged to take on their migration. But keep in mind, please,
to keep it basic. Many a developer will feel overwhelmed, should you
come back with a 600-line sample code. The net is full of that stuff
already, and it really does not help a beginner of the environment a
bit. A few lines, well commented, and easily adaptable, many times will
do a much better job. (Just for a friendly reminder).
I know a few of you already have been fooling with AutoHotkey, whereas
others might think it to be too simple for your projects. Also,
AutoHotkey might have certain challenges, due to its licensing
juristictions, but that will be a topic for you to discuss outside this
thread. For many it might be well enough, and if it will be possible
even for a blind person to create functional - if not fancy-looking -
user interfaces, this might be truly what is needed to bring your
project into a general go no matter the screen reader a user would
happen to use.
AutoHotkey is a pretty easy language to learn, from what I have
experienced, though I have never created too complicated scripts in this
environment. it does have very easy ways of setting up hotkeys, that can
be made either global, or tied to one specific application, and it can
make use of dll files, which will let you benefit from existing software
found on the net. So a few benefits over VBScript, which has been the
main language under the WinEyes environment.
Python, or the like, might be great alternatives, specially if you want
high-level apps, that Really can make your computing spin. But for the
hobby developer, maybe things like AutoHotkey will be enough for your
migration.
So once again, hope this finding will benefit someone.
--
David
_______________________________________________
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
