CuteHMI in kdereview

[M .]

 Hi,

Kevin Funk wrote:

I think you're beating a dead horse here. The ship has sailed.


I am aware all of that Don't get me wrong. I don't want to turn the tide
and convince you to use Qbs instead of CMake. I'm just pointing out: maybe
take a look at this nuclear-powered ship prototype, even tho' it hadn't
left the docks. Have been asked about Qbs, so I explained my point of view.
No reason to be concerned :P

You'll be missing out on quite a bit of tooling which is implemented in
KDE's Extra CMake Modules framework:
https://github.com/KDE/extra-cmake-modules
  (part of that is all the translation handling)
It may be hard to accomplish with CMake.

Yeah, I have been looking at ECM. It's all well done etc, but what I meant
by "components" are components like QML components. I've been using CMake
in my projects for many years, so I can compare the two. I'm not a Qbs
fanboy. CMake has its pros and advantages, but its language lacks
constructs like structures/classes/records, inheritance etc (don't want to
start another offtopic here, but I think we can all agree that CMake
language is a bit limited and its syntax is quaint...).

Then, I have deliberately written **something like** Qbs (not just Qbs). I
mentioned Qbs has some issues (I didn't want to elaborate, to not make an
offtopic, but here we are...), most important of which is that it isn't
built on top of QQmlEngine and it's not QML, but merely a QML dialect.
Imagine a proper QML-based build system, into which you could import
standard QML extensions. Integrity is something we're missing nowadays.
Still Qbs product definition files are clean and unmatched in terms of
readability, thus I think it paves the way for next-gen build system, which
will eventually replace CMake.

I hope Qbs controversy is clarified now

Regards,
Michal

sob., 15 lut 2020 o 14:11 Kevin Funk <kfunk at kde.org> napisał(a):

> On Thursday, 13 February 2020 11:00:27 CET Michal Policht wrote:
> > Yeah, I neglected translations a bit... I am going to implement adequate
> > Qbs module for extracting translations.
>
> Heya,
>
> > When it comes to Qbs, it's not dead. Community has taken over the
> > project, there's active development and recent version was released just
> > 44 days ago.
> >
> > We migrated from QMake to Qbs, when it was still supported by Qt Company
> > and promoted as official build system for Qt 6. Thus we assumed Qbs is
> > the future. We've found that Qbs has some issues (like every software),
> > but in overal it's very capable and powerful piece of software. It also
> > provides much faster builds on Windows. I wish more people would give it
> > a try before burying the project, to at least see the potential. With
> > something like Qbs we could create a build framework with reusable
> > components, so that each KDE subproject could benefit from it and become
> > naturally integrated.
>
> I think you're beating a dead horse here. The ship has sailed.
>
> You'll be missing out on quite a bit of tooling which is implemented in
> KDE's
> Extra CMake Modules framework:
>   https://github.com/KDE/extra-cmake-modules
>   (part of that is all the translation handling)
>
> There's also no support for building QBS projects on KDE's CI:
>   https://build.kde.org
>
> > It may be hard to accomplish with CMake.
>
> What exactly? I mean it's all there already.
>
> > Regards,
>
> PS: Qt's CMake-based build system just got merged into qtbase dev branch a
> few
> days ago.
>
> Regards,
> Kevin
>
>
> > Michal
> >
> > > El dilluns, 3 de febrer de 2020, a les 17:57:24 CET, Michal Policht va
> escriure:
> > >> Hello there,
> > >>
> > >> CuteHMI (https://cutehmi.kde.org/) has been moved to kdereview.
> > >
> > > It has no Messages.sh for translation extraction.
> > >
> > > Any particular reason you're using a dead build system none of our
> > > projects uses?
> > >
> > > Cheers,
> > >
> > >   Albert
> > >>
> > >> CuteHMI is meant to be a set of tools and components that help one to
> > >> create QML-based HMI/SCADA software.
> > >>
> > >> The project has been started few years ago, because I couldn't find
> any
> > >> open-source, QML-based HMI/SCADA framework I could put my things into.
> > >>
> > >> Regards
> > >>
> > >> Michal Policht
>
>
> --
> Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20200217/f88ee5cc/attachment.htm>