Qt1.0 source code
-
wrote on 31 Jul 2023, 07:25 last edited by
Do anyone keep the Qt1.0 source code and cound give me a copy?
-
@JonB I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
wrote on 1 Aug 2023, 07:20 last edited by@codeos said in Qt1.0 source code:
I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
Qt is split into several modules. Some are worth investigating, others aren't (anymore). If you stick to one module I would guess Qt is easy enough (at least not harder than v1.0) in the current version. I would expect that OS calls might have changed a lot over time (especially on Windows!!!). You would learn a lot of unnecessary stuff within this respect that you couldn't test as it is not supported anymore. You would also see a lot of awful code/ coding strategies by today's standard. Don't dig too deep into data structures not derived from QObject (like QString, QVector, etc). These were necessary at the time, but are not really useful anymore (other than Qt still relies on them). The only thing you could learn from them is copy-on-write. It is debatable if this is still the best strategy today (I don't know).
TL;DR Use the most recent version of Qt.
-
@codeos
https://download.qt.io/archive/qt/1/
good luck, have fun! -
wrote on 31 Jul 2023, 07:56 last edited by
@JonB The oldeset version is 1.41 in 'https://download.qt.io/archive/qt/1/', it seems that the version 1.0 is lost in the official sit.
-
@JonB The oldeset version is 1.41 in 'https://download.qt.io/archive/qt/1/', it seems that the version 1.0 is lost in the official sit.
-
wrote on 31 Jul 2023, 08:35 last edited by
@codeos said in Qt1.0 source code:
@JonB yes, It seems that the version 1.0 is lost in the official sit, do you keep one?
Of course not!
Just accept whatever the earliest available is, if you really think this is a good approach.
-
@codeos said in Qt1.0 source code:
@JonB yes, It seems that the version 1.0 is lost in the official sit, do you keep one?
Of course not!
Just accept whatever the earliest available is, if you really think this is a good approach.
-
@JonB I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
@codeos said in Qt1.0 source code:
the more original the more easier
But not necessarily how it is in more recent versions of Qt! Something you should consider if you want to know how modern Qt works.
-
@codeos said in Qt1.0 source code:
the more original the more easier
But not necessarily how it is in more recent versions of Qt! Something you should consider if you want to know how modern Qt works.
wrote on 1 Aug 2023, 01:44 last edited by codeos 8 Jan 2023, 01:45@jsulm Thanks for your reply， my learning will not stop at version1.0, I just want an easy start, and then step by step to learn the higher version. If I can't find the 1.0 version, I will start with the official 1.41 that I can find.
-
@JonB I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
wrote on 1 Aug 2023, 07:20 last edited by@codeos said in Qt1.0 source code:
I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
Qt is split into several modules. Some are worth investigating, others aren't (anymore). If you stick to one module I would guess Qt is easy enough (at least not harder than v1.0) in the current version. I would expect that OS calls might have changed a lot over time (especially on Windows!!!). You would learn a lot of unnecessary stuff within this respect that you couldn't test as it is not supported anymore. You would also see a lot of awful code/ coding strategies by today's standard. Don't dig too deep into data structures not derived from QObject (like QString, QVector, etc). These were necessary at the time, but are not really useful anymore (other than Qt still relies on them). The only thing you could learn from them is copy-on-write. It is debatable if this is still the best strategy today (I don't know).
TL;DR Use the most recent version of Qt.
-
@codeos said in Qt1.0 source code:
I just want the most original code to study Qt internal machanism, the more original the more easier (∩_∩)
Qt is split into several modules. Some are worth investigating, others aren't (anymore). If you stick to one module I would guess Qt is easy enough (at least not harder than v1.0) in the current version. I would expect that OS calls might have changed a lot over time (especially on Windows!!!). You would learn a lot of unnecessary stuff within this respect that you couldn't test as it is not supported anymore. You would also see a lot of awful code/ coding strategies by today's standard. Don't dig too deep into data structures not derived from QObject (like QString, QVector, etc). These were necessary at the time, but are not really useful anymore (other than Qt still relies on them). The only thing you could learn from them is copy-on-write. It is debatable if this is still the best strategy today (I don't know).
TL;DR Use the most recent version of Qt.
wrote on 2 Aug 2023, 00:06 last edited by@SimonSchroeder Thank you very much for your valuable and useful advice, I will try it.
-
C codeos has marked this topic as solved on 2 Aug 2023, 00:14
1/13