Hi Jim, I have to say I agree with all your points; in general, you'd like a much more integrated feel between the scripts interface and the window eyes interface. I did suggest something like this to GW some time back, because I wanted to add some choices into the verbosity menu (I was trying to convince them of adding a way to allow us script authors to do just this).
Now it's years later, and they didn't give me any real answer, so I'm not speaking for them; however, if I were GW, even though this sounds good for the customer, I can see GW might have a lot of support issues as people called or wrote with problems which were ultimately script problems, but because of this nice tight integration, the customer can't really tell where window eyes stops and someone else's script begins. And if a script didn't work all that well, then maybe others would think it was window-eyes which wasn't working well, and so it's reputation might be changed because of less-than-perfect scripts. And then there's the manual; GW would try and describe to the customer what some portion of window-eyes may look like to them (such as verbosity), but then it ends up being changed quite a bit by all the scripts which are running. So, even though I like this idea, I can see a lot of ways in which GW might be concerned about it. but the topic in general, of making the scripting interface smoother and easier to use, is one I'm sure could use a little more talking through, and will get it because of this thread. Oh, one more point: you mentioned having to go into the script manager in order to change something about a script's configuration or hotkeys; well, now because of the "scripts" menu, it's no longer necessary to do this (at least when script authors add an entry for their script's "help" dialog to the "scripts" menu). You can get there without going through the script manager at all. Chip -----Original Message----- From: jim grimsby Jr. [mailto:[email protected]] Sent: Saturday, January 08, 2011 3:53 PM To: Chip Orange Cc: gw-info; [email protected] Subject: Re: Script Menus: A very useful Feature! well perhaps this is not wanted feedback but it is my view on the situation so I will provide it for what it is worth. one of the biggest problems with window-eyes scripts is simply that they feel like scripts. for example if I want to set some thing in progress bars I have to do so from the progress bar menu or the script manager then I might want to configure something with auto complete then I go to that script and so on. all other window-eyes configurations of this nature is done from the verbosity dialog. like menu reading focus reading etc. it would be nice if scripts could register with the verb verbosity dialog just like everything else. so if I want to change Skype verbosity I do so from this dialog progress bar reading same place auto complete winamp etc. ok now lets talk about hot keys. window-eyes hot keys are configured from the hot keys dialog. add on scripts though have to be configured for hot keys with each keyboard manager. so if I want to change keys for Skype I have to go to the script manager then help and option and then keyboard manager and change them there. and now I want to change commands for check langwige same thing and so on. it would be nice if scripts could just register keys and said keys show up in the window-eyes hot key dialog perhaps under a section for said script but all thing are done in one place. now you got the scripts menu. the scripts menu is nice but it would be better if scripts could also register menu options in the main part of the program. for example make mouse pointer follow cursor this is clearly a mouse function and should be in the mouse menu. winamp plug-ins fire fox plug-ins behave this way. for example just plain favorites in Firefox register a favorites menu in fire fox so you can use internet explorer favorites in fire fox and add favorites to fire fox with out having to worry about if it is a book mark or favorite you got one system that does it all. this is of course a plug-in. winamp works the same way. I maintain that the scripts menu should be renamed to tools and scripts should register things there that are not appropriate for other sections of the program for example winamp alarms. otherwise there should be the ability to integrate the scripts in to the main part of the program when appropriate. example the winamp preferences should be in the verbosity dialog under a winamp group with sub sections like brows mode. this way scripts would just feel like part of the window-eyes program and be seen less to the user. hth Jim Grimsby JR. Skype name: Jim.Grimsby Skype number: 909-498-4711. E-mail: [email protected] Twitter: Jgrimsby -------------------------------------------------- From: "Chip Orange" <[email protected]> Sent: Saturday, January 08, 2011 11:18 AM To: <[email protected]> Subject: RE: Script Menus: A very useful Feature! > I too Steve have to say what a great addition it was. One other > benefit is that you no longer need to remember a hotkey for every > possible option configuration of a script; when a script author uses > the script menu for options, you can just go there, see all your > choices, and set things as you want; all without resorting to three or > more obscure hotkey sequences. > > Chip > > > -----Original Message----- > From: Steve Pattison [mailto:[email protected]] > Sent: Friday, January 07, 2011 11:38 PM > To: GW Info > Subject: Script Menus: A very useful Feature! > > Hi all, > > I'm just writing to say that I really like the Script Menus feature in WE. > I find it extremely helpful having options and help for scripts easy > to access in one menu. I hope script authors will think about > updating their scripts to use this feature if they haven't done so > already. Thanks GW Micro for making this feature available. > > Regards Steve > Email: [email protected] > MSN Messenger: [email protected] > Skype: steve1963 > Twitter: steve9782 > If you reply to this message it will be delivered to the original > sender only. If your reply would benefit others on the list and your > message is related to GW Micro, then please consider sending your > message to [email protected] so the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You > can manage your list subscription at http://www.gwmicro.com/listserv. > If you reply to this message it will be delivered to the original > sender only. If your reply would benefit others on the list and your > message is related to GW Micro, then please consider sending your > message to [email protected] so the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You > can manage your list subscription at http://www.gwmicro.com/listserv. > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
