The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.

From:

 "BX" <bronx_lab@fltg.net>

Subject:

 Re: Introduction and looking for additional resources

Date:

 Fri, Aug 2, 2013 7:53:24 am
This is a multi-part message in MIME format.

------=_NextPart_000_0018_01CE8F55.5D457BF0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Aaron,

That is OK, it makes sense from all fronts, especially those willing to file lawsuits. As was stated last year, money spent to defend ones self is a waste in the long run...

It is not easy to get code ruining under VBS and the Homer apps do assist in formulating it. I may try IronPython to see if you can extract code, but may write stuff in standard Python and merge it. That depends on who calls who...
At least the Homer stuff gives some insight on what can be called with examples but would be nice to call win32 com stuff; maybe making a python sort of shared library but it may have to be a reverse code...

Bruce

Sent: Thursday, August 01, 2013 6:28 PM
Subject: RE: Introduction and looking for additional resources


After giving this some further thought, I did want to say that GW has always been ready to share code and ideas as Aaron says, I didn't want anyone to think I was implying otherwise.



My problem is only with my lack of experience in programming difficult solutions involving use of MSAA and UIA to make a program accessible. This however, is my problem, not necessarily GW's problem, and so I should perhaps see it like that.



Chip







From: Aaron Smith [mailto:aaron@gwmicro.com]
Sent: Monday, July 29, 2013 9:08 AM
To: gw-scripting@gwmicro.com
Subject: Re: Introduction and looking for additional resources



On 7/28/2013 3:08 PM, Chip Orange wrote:



Unfortunately, GW Micro (who is the author of scripts on the advanced level) seems to no longer be making any of the apps they write open (unencrypted).


This just isn't true. There are a handful of apps that we are encrypting to keep sensitive data safe, and to hide a few routines that we don't want to just hand over to the competition, but the majority of our apps are unencrypted, and we are more than willing to share code and ideas with anyone who asks.

Aaron



-- Aaron Smith Web Development * App Development * Product Support SpecialistGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team.
------=_NextPart_000_0018_01CE8F55.5D457BF0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40"; xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>;
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23507">
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; COLOR: black; FONT-SIZE: 10pt; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.apple-style-span {
mso-style-name: apple-style-span
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: "Consolas","serif"; COLOR: black; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle21 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
..MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue bgColor=white vLink=purple>
<DIV><FONT size=2 face=Arial>Aaron,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; That is OK, it makes sense from
all fronts, especially those willing to file lawsuits. As was stated last year,
money spent to defend ones self is a waste in the long run...</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; It is not easy to get code
ruining under VBS and the Homer apps do assist in formulating it. I may try
IronPython to see if you can extract code, but may write stuff in standard
Python and merge it. That depends on who calls who...</FONT></DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; At least the Homer stuff gives
some insight on what can be called with examples but would be nice to call win32
com stuff; maybe making a python sort of shared library but it may have to be a
reverse code...</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
Bruce</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV style="FONT: 10pt arial">
<DIV><B>Sent:</B> Thursday, August 01, 2013 6:28 PM</DIV>
<DIV><B>Subject:</B> RE: Introduction and looking for additional
resources</DIV></DIV>
<DIV><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">After
giving this some further thought, I did want to say that GW has always been
ready to share code and ideas as Aaron says, I didn’t want anyone to think I was
implying otherwise.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">My
problem is only with my lack of experience in programming difficult solutions
involving use of MSAA and UIA to make a program accessible.&nbsp; This however,
is my problem, not necessarily GW’s problem, and so I should perhaps see it like
that.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Chip<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p>&nbsp;</o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt">
Aaron Smith [mailto:aaron@gwmicro.com] <BR><B>Sent:</B> Monday, July 29, 2013
9:08 AM<BR><B>To:</B> gw-scripting@gwmicro.com<BR><B>Subject:</B> Re:
Introduction and looking for additional
resources<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p>&nbsp;</o:p></P>
<P class=MsoNormal>On 7/28/2013 3:08 PM, Chip Orange
wrote:<BR><BR><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Unfortunately,
GW Micro (who is the author of scripts on the advanced level) seems to no longer
be making any of the apps they write open (unencrypted).</SPAN><o:p></o:p></P>
<P class=MsoNormal><BR>This just isn't true. There are a handful of apps that we
are encrypting to keep sensitive data safe, and to hide a few routines that we
don't want to just hand over to the competition, but the majority of our apps
are unencrypted, and we are more than willing to share code and ideas with
anyone who asks. <BR><BR>Aaron<BR><BR><o:p></o:p></P><PRE>-- <o:p></o:p></PRE><PRE>Aaron Smith <o:p></o:p></PRE><PRE>Web Development * App Development * Product Support Specialist<o:p></o:p></PRE><PRE>GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825<o:p></o:p></PRE><PRE>260-489-3671 * gwmicro.com<o:p></o:p></PRE><PRE><o:p>&nbsp;</o:p></PRE><PRE>To insure that you receive proper support, please include all past<o:p></o:p></PRE><PRE>correspondence (where applicable), and any relevant information<o:p></o:p></PRE><PRE>pertinent to your situation when submitting a problem report to the GW<o:p></o:p></PRE><PRE>Micro Technical Support Team.<o:p></o:p></PRE></DIV></BODY></HTML>

------=_NextPart_000_0018_01CE8F55.5D457BF0--