Skip to content
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

Open
Varriount opened this issue Jul 7, 2020 · 3 comments
Open

Recommended way to contribute? #53

Varriount opened this issue Jul 7, 2020 · 3 comments

Comments

@Varriount
Copy link

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.

@khchen
Copy link
Owner

khchen commented Jul 8, 2020

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.

@khchen
Copy link
Owner

khchen commented Dec 3, 2020

I added uiautomation module and a simple example.
However, I am not familiar with uiautomation, maybe you can test it?

@nc-x
Copy link

nc-x commented Feb 2, 2021

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.

Windows Api bindings can now be generated using https://github.com/microsoft/win32metadata, so it should be easier to automate everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants