On 13/05/2014 2:57 PM, Eric S. Johansson wrote:
back in 1999ish, joel gould wrote the following and I want to know if it is still true. am planning on converting the 2.7ish natlink to 3.X some time over the next year. need to decide if I should leave the C++ code alone or can we go pure python?
It hasn't changed for this use-case, so a pure-python solution probably isn't viable (unless you want to investigate using comtypes).
HTH, Mark.
----------------------------- The first step in developing the NatLink Python macro system was to develop a Python extension module. This Python extension module, written in C++, provides an interface to the Dragon NaturallySpeaking native APIs from Python scripts. As described above, the Dragon NaturallySpeaking APIs are based on custom COM interfaces. Because they use custom COM interfaces instead of OLE automation, it was not possible to use Mark Hammond’s PythonCOM system [4]. In addition, conventional Python wrapping technology, like SWIG [10] or Py_cpp [11], is designed for libraries that expose C or C++ APIs, not COM interfaces. So that technology could not be used either. Instead I wrote custom C++ code to export a selected set of objects and functions from the Dragon NaturallySpeaking APIs. The extension module is called natlink.dll and can be used from Python by importing “natlink”. _______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
