@thread

GL rendering for normal windows is now enabled. This is an example:

Deform (GL)

Deform (no GL)

The pretty one is the soft render. The ugly one is the GL (ogles2). Speed is the same.

@thread

Shader stack on OS4 is too rudimentary for QtQuick3D to render anything. Sorry guys, had hoped for that victory.

@Maijestro

We are not fully ready to release yet. Qt6 needs some components that are their own entities. It will probably not be long, since, as you see, everything works - quite acurately - right out of the box.

Of course, if you are impatient, everything is available at the source code level, and it should only take about 14 days of hard, nonstop labor to get a working executable - if you are lucky.

I sincerely hope, you have fun with it, whenever it gets out there. Otherwise everything has surely been in vain. Best of all to everyone.

@FlynnTheAvatar

Now THAT is really satisfying... I like the mood, it makes me feel so - saturated! It also gives me the impression, that this is something really, really valuable to look at, here in my nightgown getting ready to voluntarily shut down my circuitry until the day tomorrow, where I have to perform dastardly feats against an unbeknownst enemy. I have to say, that is extraordinary! I am just waiting for everyone else to join in and have a caballesque (whatever that is).

@FlynnTheAvatar

That's fabulous! Now - for the devil within me: Could we have some music on top of that?? Not the slightest of what I'm after, so anything will do, just any music at all! Can you do that for me!? Oh the joys of laughter, wo-ho-ho, beyond the wild canyon where the roses grow....!

...And perhaps also tell me: How do people normally upload images in posts here?? I had to let go of my homepage service, so I am left with cloud storage, that doesn't play so well with the [img] function here.

@FlynnTheAvatar

You did an absolutely amazing job. We can all see everything loud and clear! Nothing is hidden, everything is written - in vast codes of orbital noise, beridden with fearless joy and laughter... Ho-ho-ho! Do the moose dance and join the quest for glory -

IN THE TAQTUC Challenge 2026........(!!)

@LiveForIt

Well, I call parsimony, and the fact that I have done absolutely nothing to prevent the blue bar from going under. As a matter of fact I have followed the logic prepared by whomever took the liberty and do the jumble for the rumble of putting things in certain places in the window-holder factorization entities.

If, on the other hand, parsimony is not an option, I could also give the conceptual argument, that the lower part of the window is where the Qt specific status bars go in QMainWindow driven settings. So it would not be good value of visuality to put another bar there to puke on.

If it is good value to you to keep things straight up and running, I will do absolutely nothing about it. I think there should be an entry on this put in the documentation of the subject - not to clearly cut the differences involved, but rather to haunt you in your sleep, when you least want to see bars of blue turn golden in an abstained vision of corporeal nature in the hidden unknown.

Over and easy.

@joerg

Quote:

So in fact one should expect incompatible changes on a version increment.

Now, while we're at it, I would love to admit, that it is totally my mistake, that the version bump had to be made. We could have made it backwards compatible. But we chose the cleaner option with less clutter. Appologies.

@joerg

Quote:

Well, given the fact, that Amiga uses libraries that are cross platform, we now need to reinforce this standard on the rest of the world.

@TheMagicSN

clib4_libs_adtools.tar.gz

For anyone who is interested in a spoken introduction:

Qt6 Showcase at AmigaLabs on Discord this Sunday at 19:00 pm CET

@TheMagicSN

Please look in mkspecs/amiga-g++/qmake.conf. This should give you the order of linkage. But to be clear : Doing this manually really defies the purpose of Qt. I will stop commenting on the issue, until you create and use a proper qmake project.

@TheMagicSN

Just to try and keep up with your pace - what you want to do with the Qt sources is probably to create a .pro file for them (in case this doesn't exist alread!). This is very easy, look here :

Qmake tutorial

Run

> qmake-amige

On the .pro file to get the Makefile and configuration items.

Then, if you really want to link this part together with the rest of the objects, you can either copy-paste whatever command lines you need from the Makefile OR you can create some super-level project generator or Makefile that handles the conglomeration facilitation of the project. If your issue is, that you are building it on the Amiga (what a feat, damn...), then I can congratulate you : The build ituls work on the Amiga, just not right now. There will be news on this item at some point, I assure you.

@TheMagicSN

icu for Qt6

@TheMagicSN

LibsPorts at AmigaLabs

@TheMagicSN

Hmm, strange. I have not seen this before. Well, one thing I am curious about is, if the authors intended it that way or if this is specific to the amiga port. Or maybe you created it entirely by youself, which is a massive achievement, but there are certain guiding rules for how these things are best managed. To subtract the amount of stress it would have, trying to maintain these things on non-standardized bases. Well, to tell you one thing - you need to adapt your build tools to compile and link against clib4. For this you might need a new compiler. If that is a longshot, then you are better off waiting for a little bit, until we can get you a hosted entity, that builds it for you in the correct way. Essentially, what you are looking for, is something that is being made and not quite ready yet. Hope you can entertain youself in the meantime. If you get anxious and rhubarb yourself over the terrain of interesting fortunes, then I would say - get core in last then network and gui. Then widgets. Then the rest. If you try and fail, then that's ok with me. We will get there. Cincerely. Good luck.

@Maijestro

Quote:

I suppose, that once in a very distant future, we will have individual Qt6 apps not take up so much space (really, it is _ridiculous_ at the moment, there is nothing more to say about it), and then every app will be directed to where it is intended. I thought in this case, that I would just preserve the situation, that the user created for him/herself by the unpacking condition and leave the apps in that special place. I could have been misjudging, sure, but maybe it is time for a change, another way of living, where apps are not just copied again and again, and where there is something about the originating intention, that stays alive along the way. It is up to you to decide. I will gladly stand for the posibility, that linking will be done, as the fathers saw it in the distant sands. And you might think, I am nuts, but it is only 'till you see the livelyhood of the things, these circuits can do. To me and you. And foo. And bar.

@TheMagicSN

The last item on the command line is a giveaway : Your project somehow tries to link dynamically, which is not supported by current standards.

What kind of build is this? I assume cmake, but you never know, so I ask. If you are using cmake, then you HAVE TO use /qt-cmake-amiga in place of any cmake command OR at least look in this (text) file and incorporate everything there, so nothing is missing from the configure step. THEN you will have to persistently convince the configuration to do a static build, otherwise nothing is going to work at present.

Also you need all the additional libraries for the build. Maybe that is just what you are asking. I am using a mixture of ready packaged libraries from the ExperimentalSDK in some earlier version combined with probably some selected up-to-date ones. If you give me enough time, I will share with you my entire library setup, I just have to figure out which parts to omit, so it doesn't fill up the entire living room.

Your favorite apps have become updated :

favApps on github