On Thu, 23 Mar 2017 08:46:27 -0700 (PDT) "Eric S. Johansson" <[email protected]> wrote:
> On Thursday, March 23, 2017 at 10:47:46 AM UTC-4, Terry Brown wrote: > > > > It might, but it also might be hard to get that route to work, and > > there might be easier alternatives. > > > > If NaturallySpeaking could be smarter about working out what you're > > doing, maybe by looking at the window title as well as the > > executable, it would help - I couldn't quickly google up any docs. > > on how NS associates grammar rules with programs. > > We had a package called natlink that allowed us to control the > Association of grammar to some aspect of the program. For the most > part it was title bar contents (dodgy technique) or executable name > (slightly less dodgy). I don't think titlebar is dodgy as long as the matching can look for patterns like "ends with '.leo'". If necessary, adding some target text to Leo's titlebar wouldn't be hard. > > If it is based solely on the exe, the easiest way might be to (have > > someone) compile a very short C program which uses system() to > > invoke Leo - not sure if that would work, but if NS picked up on > > the exe of the wrapper program instead of Python, you could make > > that name anything you wanted. > > Why wouldn't py2exe work? Is there something magic about Leo? By the The problem is that there's nothing magic about py2exe, I'm not sure how many issues you'd run into in terms of it installing required dependencies etc. But maybe if everything's installed in the right places you can just convert launchLeo.py to an exe. I don't know how py2exe handles import paths. Cheers -Terry > way, I have the same problem with web-based applications. However, I > will thank you for triggering a? In my mind. I use a third-party > extension called know-brainer and that might give me the ability to > bind by title bar. It should work as long as the title bar remains > relatively constant. > > > I wonder what https://github.com/chajadan/DragonflyRules is doing? > > Oh this is another way nuance has ***ked over disabled. This package, > like a few other community supported toolkits uses the previously > mentioned toolkit. Nuance broke this package just like they have in > multiple releases but this time we can't find a fix. So now we are > stuck with Visual Basic in a very captive environment. This is why I > would like to make Leo speech-enabled using something like Google's > speech recognition engine but I can't get there without making > NaturallySpeaking work in the short term. > > Just experienced another OBH moment. The Leo Windows installer counts > on a 32-bit Windows. As does the spellchecking tool. Sucks if you > need a 64-bit Python environment. > > It feels like a Monday… -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
