Qt - work in progress

New SDK available:

http://dl.dropbox.com/u/5482530/Qt/qt ... rce-microsdk-4.6.2.tar.gz

It requires amicygnix and the amicygnix SDK.


If you just want to watch, there are a couple of random examples:

http://dl.dropbox.com/u/5482530/Qt/qt ... nix-examples-4.6.2.tar.gz

Examples only requires amicygnix base, no SDK. Please run from Workbench!



And finally, if you are in for the big lebowski, here is my complete source archive:

http://dl.dropbox.com/u/5482530/Qt/qt ... mpletesource-4.6.2.tar.gz

Requires: Patience, lots of patience and spare time...


Happy coding!

@alfkil

So this allows others to port QT applications to OS4/AmiCygnix? Cool! I don't remember WxWidgets being in the previous AmiCygnix SDK, I'm looking forward to that one until the amigabounty native port is completed.

@alfkil

QT was really nice to have...
Any eta on OS4.x native version? and...
Maybe we can add a bounty to create a workgroup to help in the port?

@alfkil

Really good news !

@alfkil

awesome! opens so many possibilities! Respect to you sir (and Edgar for Amicygnix of course!)!!! :)

@all:

First of all: Don't get your hopes up too high. A lot of features are working, but a lot is also missing. As you will see, only 4 libraries are available now. QtGui has problems with threads that I have been banging my head against for some time with no success. Basically, if you add any gui element that opens a thread (like a file requester), you are going to get into trouble.

I'm going to work on a different project for some time now, so I wanted to share the project at it's current level. Of course I'm going to work on it again in the future, and of course any help would be appreciated

About the sources:

1) Stay away from the configure script!
2) Use 'gmake staticlib' to build any library, as dynamic linking is not available at this stage

@alfkil

Quote:

a new one on AOS4.1U2 (in case not allready installed).

@Mrodfr

I installed update 2, and it didn't solve the issue. Sadly :-I

@alfkil

Alas, I was wrong again: Update 2 _did_ solve the problem, the file dialog problem was just an entirely different issue. Now Qt works with both dock widgets and file dialogs :) (update uploaded soon).

@alfkil

Sound great.
Thanks for the news.

Project started at qt.gitorious:

http://gitorious.org/qt-for-amicygnix-amiga-os-4-1

Also updates of SDK and examples uploaded to os4depot (now without debug data ).


Things to be done next:
jpg support doesn't work
there is a timing issue, so animations are slooow
(+more)

@alfkil

Tried your demos and I must admit that never I though it could be possible to see a QT app on my little Sam! Impressed!
Yes, of course with my cpu speed its dead slow, but faster ones are coming so it is really great to have QT supported on our (well, on AmiCygnix at least) platform!
Thanks!

Hej Alfkil
Looks very promising, keep up the good work.

@virgola
If QT can work fast on a mobile phone (and yes it does, at least on the Nokia N900) then it should be possible on the Sam440 too. Of course it might require a lot of optimisation work...

@ChrisH

Imho the major slowing down there is because of Amycygnix as a layer. For sure if it will be done some day native, it will be faster even without code-optimisation.

@kas1e + others

I think the big slowdown is some obscure timing issue, because in several
of the demos I can "speed up" animation by moving the mouse in front
of it.

About a native port: It is very unlikely that I will find time and (not least)
energy to do it. Qt is a monster, and the only real reason that I have
come so far, is because of Edgar and amicygnix. I'm going to try and
finish the amicygnix port, and then I hope somebody will be so
inspired, that they dive in and finish the job

@ChrisH

OT:
N900 is a beast of mobile PC, not just a phone
Even internet browsing is faster on that thing than on Sam440ep.

back on topic:
It would be great to have QT on AmiCygnix/AmigaOS.
Thanks for trying!

nexus

@nexus Quote:
The only aspect relevant to this discussion is the CPU power, and that is "only" a 600?MHz ARM Cortex-A8 CPU. Without knowing the details of it, I assume this is in the same ball-park as the Sam440's.

Quote:
It probably has JIT Javascript, plus it only has to handle 800 ? 480 pixels (which is 3.4 times less pixels than 1280x1024). Probably some other reasons as well.

@ChrisH

I don't think that the resolution is here important (with respect to internet browsing) because the entire side has do be loaded and displayed. On 800x480 it even has to additional scale the page in a way such that it is entirely visible.

But if you insist that the resolution has an important impact, then this is also true (for sure) for QT applications. And on N900 there is no need to scale an QT application down. QT applications on N900 are designed for N900's resolution (and are relatively simple as far as i have seen some). So, I guess, QT on Amiga/AmiCygnix & Sam440ep (and higher resolutions) will naturally be slower than on N900.

regards,
nexus

@nexus

Nokia bought Trolltech some times ago as such they have in house guys that designed and programmed Qt. They also are a relatively big company with comfortable budget.
As a consequence they have highly skilled Qt programmer and plenty of financial resources to fine tune their N900 Qt port. I think this is to put in comparison with a spare time project done by a Qt user (even a very skilled one can't compete with a Qt developer) as to why one is faster than the other.
I don't think this has anything to do with the CPU...