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

A way to "sponsor" a feature? #998

Open
dzek69 opened this issue Feb 16, 2023 · 3 comments
Open

A way to "sponsor" a feature? #998

dzek69 opened this issue Feb 16, 2023 · 3 comments

Comments

@dzek69
Copy link

dzek69 commented Feb 16, 2023

Is your feature request related to a problem? Please describe.
I started developing an app using node gui few months ago, but I stopped when I bumped a problem I could not solve, because a needed QT binding is not ready yet.

While from high level perspective it seems to be a pretty quick fix - I'm too bad with any low level programming to be able to solve this myself and start a PR.

Also I expect to find more issues in the future, even that single one is fixed.

Describe the solution you'd like
I'd like to be able to "sponsor" a features I might need, so I can progress with building the application. There are some projects that helps organize such requests, but I don't remember any name. But a simple approach is just the question: Can I pay you to prioritize my needs?

Describe alternatives you've considered
Learning C++ 🤷🏻‍♂️

Additional context
none

@sedwards2009
Copy link
Collaborator

Which binding / API are we talking about here?

@dzek69
Copy link
Author

dzek69 commented Mar 4, 2023

My current problem:

I want to write custom data into clipboard.

setData of QMimeData is now missing:

// Napi::Value setData(const Napi::CallbackInfo& info);

And QClipboard should of course support setMimeData

--

Still, that's just one thing, I could find more blockers in the future. I'd love to donate something each time you implement something that unblocks me :)

@sedwards2009
Copy link
Collaborator

You can also give it a try yourself. QMimeData.ts, qmimedata_wrap.h, and qmimedata_wrap.cpp will need updates. setData() should take a node js Buffer for the data part instead of QByteArray. There is already a QPixmap.loadFromData() method out there which is very close to what you want to do for the C++ parts.

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

2 participants