github-starred/qmlnet

Fork 0

mirror of https://github.com/qmlnet/qmlnet.git synced 2026-05-15 14:15:54 -06:00

[GH-ISSUE #240] Help. I don't have extra time to dedicate to this anymore. #155

New issue

Open

opened 2026-05-05 11:07:02 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 11:07:02 -06:00

Owner

Originally created by @pauldotknopf on GitHub (May 17, 2021).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/240

Let me say this. This project works great for my needs. I use it in production, and will likely use it for more projects going forward.

There are many people wanting features/things that are outside of scope of what I need for my projects.

After having a kid and playing live music more and more, I have less and less time that I'm willing to allocate to this project that doesn't serve my professional work.

With that said, I'm wondering if I should update the README.md to make this up-front and explicit. Thoughts?

Originally created by @pauldotknopf on GitHub (May 17, 2021). Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/240 Let me say this. This project works great for my needs. I use it in production, and will likely use it for more projects going forward. There are many people wanting features/things that are outside of scope of what **I need** for **my** projects. After having a kid and playing live music more and more, I have less and less time that I'm willing to allocate to this project that doesn't serve my professional work. With that said, I'm wondering if I should update the ```README.md``` to make this up-front and explicit. Thoughts?

gitea-mirror added the

question

label 2026-05-05 11:07:02 -06:00

gitea-mirror commented

2026-05-05 11:07:03 -06:00

Author

Owner

@vadi2 commented on GitHub (May 17, 2021):

I think that would be a good idea 👍

@vadi2 commented on GitHub (May 17, 2021): I think that would be a good idea :+1:

gitea-mirror commented

2026-05-05 11:07:05 -06:00

Author

Owner

@timunie commented on GitHub (May 17, 2021):

Hi @pauldotknopf

If I were you I would write this on the main page. Moreover I would think about using the discussion section of GitHub as some ideas may be useful for you as well. But this is just an opinion of a free time and self-taught programmer, so maybe it's different for you.

Anyway thank you for sharing this project.

Happy coding
Tim

@timunie commented on GitHub (May 17, 2021): Hi @pauldotknopf If I were you I would write this on the main page. Moreover I would think about using the discussion section of GitHub as some ideas may be useful for you as well. But this is just an opinion of a free time and self-taught programmer, so maybe it's different for you. Anyway thank you for sharing this project. Happy coding Tim

gitea-mirror commented

2026-05-05 11:07:05 -06:00

Author

Owner

@vadi2 commented on GitHub (May 17, 2021):

Could you think on how to do releases going forward? The un-released https://github.com/qmlnet/qmlnet/pull/219 adds simple window icon support, but not being on nuget, it's difficult to use.

@vadi2 commented on GitHub (May 17, 2021): Could you think on how to do releases going forward? The un-released https://github.com/qmlnet/qmlnet/pull/219 adds simple window icon support, but not being on nuget, it's difficult to use.

gitea-mirror commented

2026-05-05 11:07:06 -06:00

Author

Owner

@FieryRider commented on GitHub (May 17, 2021):

Yeah, updating the README.md will be the best IMO. What about pull request? Will you merge those in the future?

@FieryRider commented on GitHub (May 17, 2021): Yeah, updating the `README.md` will be the best IMO. What about pull request? Will you merge those in the future?

gitea-mirror commented

2026-05-05 11:07:07 -06:00

Author

Owner

@dev693 commented on GitHub (Oct 7, 2021):

Hi @pauldotknopf,
Maybe you remember we had a call and talked once about some bugfixes in Qml.Net because we use it as our UI Framework for our product Visoplan. I and our company will for sure spent time on this. So if you need Help I'm willing to help or even more.

@dev693 commented on GitHub (Oct 7, 2021): Hi @pauldotknopf, Maybe you remember we had a call and talked once about some bugfixes in Qml.Net because we use it as our UI Framework for our product Visoplan. I and our company will for sure spent time on this. So if you need Help I'm willing to help or even more.

gitea-mirror commented

2026-05-05 11:07:07 -06:00

Author

Owner

@scherenhaenden commented on GitHub (Jul 28, 2022):

I'm gonna fork this and see if I can come forward to update a few things and send a PR.

@scherenhaenden commented on GitHub (Jul 28, 2022): I'm gonna fork this and see if I can come forward to update a few things and send a PR.

gitea-mirror commented

2026-05-05 11:07:08 -06:00

Author

Owner

@MV10 commented on GitHub (Nov 23, 2025):

I'd have liked to see this disclosed in the README, too.

I have the time and programming experience to help out, but don't know anything about QT (yet), unfortunately.

@MV10 commented on GitHub (Nov 23, 2025): I'd have liked to see this disclosed in the README, too. I have the time and programming experience to help out, but don't know anything about QT (yet), unfortunately.