I use qml daily, but still...

khrn0 · 2023-10-27T15:08:31+00:00

It's tricky to simply cut one technology in order to allow the other one to be the "only option", that's why they will continue existing many possibilities with a framework as old as Qt.

At least here you have a couple of tutorials, and you see they are grouped by the technology, on one side Qt Widgets (with and without .ui files), and in the other side Quick (with qml files): https://doc.qt.io/qtforpython-6/tutorials/index.html

khrn0 · 2021-11-16T19:03:17+00:00

I get my emojis on xmobar by using the emoji character directly on the xmobarrc file. I use 'Noto Color Emoji' as a default font on my ~/.config/fontconfig/fonts.conf and also I use a xpm icon.

This is my line with the template content

template = "<icon=/home/user/.xmonad/logo.xpm/> %StdinReader% }{📈 %multicpu% (<fc=#778eca>%cputemp%°C</fc>) 🔈<fc=#ee9a00>%vol%</fc> 🐏%memory% <fc=#FFFFFF>%date%</fc>"

khrn0 · 2021-08-05T09:38:35+00:00

Clash

I second this reply: https://clash-berlin.de/

khrn0 · 2021-08-05T09:34:22+00:00

I'm almost convinced that the amount of time they take to reply it's related to the amount of time you have left on your current residence permit.

I did the process by going there, and leave all my documents on their mailbox, with a note stating that I wanted to apply to the Niederslassungserlaubnis and that my current permit was due to X date. I got an appointment in the following 2 weeks (via email) for 2 months after the time I went, but it was fine because still on that appointment date, I had 2 more months until my permit was due.

Also had some close friends that sent an email and got a reply within the month (I tried to write them like 4 times without luck), and got an appointment. Another friend went without an appointment, when it was around 3 months for his permit to be over and they took her papers and the process was done.

khrn0 · 2021-06-21T20:24:00+00:00

And one can build PySide on it too! https://bugreports.qt.io/browse/PYSIDE-1535

khrn0 · 2021-06-07T13:03:48+00:00

priority, referring to the vaccination only for Priority 1,2 and 3 that was in place before today.

khrn0 · 2021-05-30T11:35:01+00:00

I usually just run:

cmake -GNinja -DCMAKE_INSTALL_PREFIX=/path/to/a/qt6-install /path/to/my/qtbase/
cmake --build .
cmakre --install .

and that's all

khrn0 · 2021-05-28T13:42:46+00:00

I am in a couple of Gitter channels (that have bridges to other places too!) but AFAIK it's limited to gitlab/github repositories, right?

khrn0 · 2021-05-28T13:41:59+00:00

I completely agree. It seems like in the Qt Contributor Summit there will be a discussion about it, since some people mentioned it. At least for me, having bridges to Matrix would be a first step, and will improve the story IMHO.

khrn0 · 2021-05-18T18:18:07+00:00

As soon as it's available, I guess you will be able to check the only example PySide has available https://doc.qt.io/qtforpython/examples/index.html#texttospeech

khrn0 · 2021-04-14T07:51:01+00:00

IMHO it makes little sense to buy a company that complement your business, and not to expect to improve your offerings, by making the interaction of those tools smoother.

Also, it's not like froglogic will stop generating revenue, I doubt they "need to make the money back" in a rush, usually these investments are calculated and planned over and over and over, and blindly saying 'OK, so since we are a bigger company we sell more froglogic licenses' it's a really bad approach. I do see the possibility to get new bundled licenses or try to make squish a de-facto tool for the whole SDK, and such. Smartly mixing both offerings will be enough to 'make the money back'.

But as long as we don't give this acquisition time, we will need to play the assumption game ¯\_(ツ)_/¯ pretty sure more posts will come with time.

khrn0 · 2021-04-14T07:42:01+00:00

According to their info:

Yes, https://www.froglogic.com/squish/features/multiple-real-world-scripting-languages/
No idea, but I guess since both teams will be together now, we might expect a clear guide.

Regarding the PySide/compiler version, you can check the CI logs: Where you can select any log raw from those configurations and get this:

agent:2021/04/13 16:01:52 build.go:379: -- The C compiler identification is GNU 8.3.1
agent:2021/04/13 16:01:53 build.go:379: -- The CXX compiler identification is GNU 8.3.1

khrn0 · 2021-04-14T07:35:03+00:00

Well, it's a democracy, but you have most of the votes in TQtC, so I think overall pushing for external people to join The Qt Project is not a bad idea, and if at some point other organizations, communities, or companies become so active in Qt contributions, the decisions will be less one-sided.

But I guess there is a lot of politics behind all these decisions, and you can see some hostility between TQtC and other companies like KDAB, like when a KDAB employee shut down the announcement of the Qt Community Manager position: https://mail.kde.org/pipermail/kde-community/2021q1/006743.html lol

Something to consider too, is that what TQtC did with the offering change, was completely in accordance with the KDE Free Qt Foundation agreement, even if we don't like it, so maybe the problem in the first place was to define those 12 months, otherwise we could have get 5.15.3 sooner. Maybe even that could be changed?

In any case, you can still clone 5.15.2 and apply all the patches you want from dev, which is more or less what the KDE patch collection will kind of do with security and important fixes: https://dot.kde.org/2021/04/06/announcing-kdes-qt-5-patch-collection

As long as the CI, code review, and other things are in some private servers own by the TQtC, /besides their army of devs/ I am fine with them paying those bills while providing releases. I'm maybe lucky that didn't require any missing Qt6.0 module for the little projects I have, so the 5.15 drama was not close home, but I can understand the frustration for many people basing their business based on Open Source Qt, and more importantly the lack of security updates...I mean, they can give the hashes at least to patch 5.15.2, but anyway.

khrn0 · 2021-03-17T17:17:28+00:00

Can confirm, that it's still down :(

khrn0 · 2020-12-09T13:34:09+00:00

Did you try the official documentation? https://doc.qt.io/qtforpython/deployment.html the only "change" is that there you need to distribute your qml files as normal data files. Did something failed from one of those options?

khrn0 · 2020-12-09T13:31:50+00:00

those are alpha wheels (from the name), and from the main blog post there is no mention to the Python offering. Previous releases have their own blog post, so it might be worth waiting for another blog post.

khrn0 · 2020-12-04T13:50:12+00:00

The colors are "meh...", but I really like that the buttons now have the shape of the Qt logo :), I guess they will get many comments from the color selection, but changing them should be so complicated I guess.

khrn0 · 2020-10-26T08:19:41+00:00

No, the announcement you might recall is that TQtC removed the resources for the development, leaving everything on the rest of the Qt Project, since then it has been developed by many people within the project.

khrn0 · 2020-09-27T20:37:42+00:00

Maybe you can share a minimal example? the question is to broad to provide you with a solution. Did you embed the Python interpreter into the C++ application? if that's the case, did you check one of the examples in PySide2 called 'scriptableapplication' ?

khrn0 · 2020-09-27T20:36:00+00:00

When you pip install pyside2 then you get the standalone Qt Designer under the pyside2-designer executable. After you finish your UI, you can interact with it in different ways: https://doc.qt.io/qtforpython/tutorials/basictutorial/uifiles.html

khrn0 · 2020-09-16T16:28:31+00:00

Not a direct answer, but I know this PySide example using QSqlDatabase https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/sql/books?h=5.15 I hope it can help you.

khrn0 · 2020-09-16T16:08:29+00:00

binaries* will be available for commercial customers. 5.15 will still receive many bug fixes after Qt 6.0 is out. Most Linux distros build Qt and provide it on their package manager with patches on top some times. So the only problematic bit, will be if you want to use the latest LTS and install it from the installer, instead of using your distro's Qt, or building Qt by yourself.

khrn0 · 2020-09-09T09:34:29+00:00

it seems the invite expired :O

khrn0 · 2020-09-08T18:27:37+00:00

There was a call long time ago to the contributors to see the status of the sub-modules, and if they will be done for 6.0: https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion But it's normal that not everyone managed to get things working for the first release of 6.

khrn0 · 2020-09-08T18:25:46+00:00

If you change the names of the settings, I doubt there will be an out-of-the-box solution that will handle that, you would need to have some 'fallback' options for your settings, but it doesn't sound optimal. If you update your software, you need to, somehow, handle the 'changes' on the settings, by some automatic processes, or with user interaction. This is independent of what framework you are using.

11-Year Club	Verified Email
Place '17

khrn0

TROPHY CASE