3 ms·

Small tip: put a working example when you advertise such an API with a screenshot as a bonus. As a developer I want to see if the bindings feel natural and mayb

by gbin 5y ago

Small tip: put a working example when you advertise such an API with a screenshot as a bonus. As a developer I want to see if the bindings feel natural and maybe try it right away. Here both the article and the GitHub readme lack this.

Kelteseth 5y ago
There is an example folder https://github.com/KDAB/cxx-qt/tree/main/examples https://github.com/KDAB/cxx-qt/tree/main/examples
- detaro 5y ago
  And the start of the "book" also explains an example: https://kdab.github.io/cxx-qt/book/getting-started/2-our-first-cxx-qt-module.html https://kdab.github.io/cxx-qt/book/getting-started/2-our-fir... Fully agreed that should be more obvious though.
  - simlevesque 5y ago
    The first comment says specifically "screenshot" but the links you and the person you replied to mentionned both have no screenshot. We want screenshots. Images of the end product GUI.
    - detaro 5y ago
      It' says "a working example" - which we referenced. With "a screenshot as a bonus". And a screenshot is pretty pointless for a binding library, since it doesn't impact what the GUI looks like, so it's not surprising a simple example to show the code doesn't have one. EDIT: i.e. after looking at the QML, from quick glance it'll render two lines of text and two buttons in QML default styling. What do you gain from that?
    - rat9988 5y ago
      Honestly no one needs screenshot. It's not showcasing a gui framework, but a binding to an existing one. I'd go as far to say that if you need screenshot for this, you may not be their primary audience.
melony 5y ago
And screenshots!
- marcosdumay 5y ago
  Although I agree that screenshots will attract some people, it's Qt. The look and feel won't be any different from any other Qt application (or better, it will be completely dependent on theming, so the pictures won't even reflect what you get.)

3 ms·

Small tip: put a working example when you advertise such an API with a screenshot as a bonus. As a developer I want to see if the bindings feel natural and mayb

by gbin 5y ago

Kelteseth 5y ago
There is an example folder https://github.com/KDAB/cxx-qt/tree/main/examples https://github.com/KDAB/cxx-qt/tree/main/examples
- detaro 5y ago
  And the start of the "book" also explains an example: https://kdab.github.io/cxx-qt/book/getting-started/2-our-first-cxx-qt-module.html https://kdab.github.io/cxx-qt/book/getting-started/2-our-fir... Fully agreed that should be more obvious though.
  - simlevesque 5y ago
    The first comment says specifically "screenshot" but the links you and the person you replied to mentionned both have no screenshot. We want screenshots. Images of the end product GUI.
    - detaro 5y ago
      It' says "a working example" - which we referenced. With "a screenshot as a bonus". And a screenshot is pretty pointless for a binding library, since it doesn't impact what the GUI looks like, so it's not surprising a simple example to show the code doesn't have one. EDIT: i.e. after looking at the QML, from quick glance it'll render two lines of text and two buttons in QML default styling. What do you gain from that?
    - rat9988 5y ago
      Honestly no one needs screenshot. It's not showcasing a gui framework, but a binding to an existing one. I'd go as far to say that if you need screenshot for this, you may not be their primary audience.
melony 5y ago
And screenshots!
- marcosdumay 5y ago
  Although I agree that screenshots will attract some people, it's Qt. The look and feel won't be any different from any other Qt application (or better, it will be completely dependent on theming, so the pictures won't even reflect what you get.)