Hi Kevin, where I work I write ms word scripts for our users, and I sometimes do add an additional menu pad to the standard Word menu (this is in 2003). I then provide menu choices in this menu for the script(s) associated with the template in use; I name the menu pad something related to the template name so the user should recognize it's obviously not one of the standard Word menus.
It is possible to, but I don't, modify the standard Word menus themselves; you could just add an additional choice to the edit menu for instance if you wanted to. Oh wait, in one template I do modify the standard context menu by adding some additional choices. Is this what you were asking? Chip -----Original Message----- From: Kevin Huber [mailto:kevin.hub...@gmail.com] Sent: Monday, January 10, 2011 10:21 AM To: gw-scripting Subject: Re: Script Menus: A very useful Feature! Hi Jim: Have you seen MS Word scripts or MS Excel scipts, for example? Are they any different? I don't know because I haven't had any experience with them, I am just curious how they integrate into their respective programs. Kevin Huber On 1/8/11, jim grimsby Jr. <jgrim...@roadrunner.com> wrote: > 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: jgrim...@roadrunner.com > Twitter: Jgrimsby > > -------------------------------------------------- > From: "Chip Orange" <lists3...@comcast.net> > Sent: Saturday, January 08, 2011 11:18 AM > To: <gw-i...@gwmicro.com> > 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:s...@internode.on.net] >> 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: s...@internode.on.net >> MSN Messenger: internetuser...@hotmail.com >> 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 gw-i...@gwmicro.com 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 gw-i...@gwmicro.com 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. >> >
