-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended way to contribute? #53
Comments
Hmm... When I start this projects, I decide to translate MinGW's Windows headers to nim instead of using Microsoft Windows 10 SDK. Because it seems more easily. Until now, my own mingw2nim already contains about 6000 lines of code, hundreds PEGs, uncountable hotpatches, etc. Now, I regret that why I don't use Windows 10 SDK at the beginning. It seems that I need to redo all my work on Win10SDK to add the features that not supported in MinGW. In fact, I tried parse win10sdk a while ago (and yes, for UI automation), by npeg instead of std/pegs, in very slow progress, and I almost gave up. Another way to do is trying not to parse whole win10sdk but only UI automation part. I don't know is it easy or not. BTW, I am still using sublime text. Thanks for your NimLime. |
I added uiautomation module and a simple example. |
Windows Api bindings can now be generated using https://github.com/microsoft/win32metadata, so it should be easier to automate everything. |
I'd like to add some more libraries (namely the UI automation libraries). Is there a recommended process/workflow for doing this? I'm familiar with C2Nim, but it struggles to generate accurate code, given the complexity of the Windows API.
The text was updated successfully, but these errors were encountered: