Q3support status in the next Qt release - qt

What is the status of q3support classes in the next Qt release, I heard that before august when next major Qt release it will be done without Qt3 support is that true? please give me links if that is true.
And what is the proposed ways to reduce the q3 dependencies.

Here you go: http://labs.qt.nokia.com/2011/05/12/qt-modules-maturity-level-the-list/
For future... why won't use google? Qt3Support is already deprecated and will be dropped in Qt5. And the proposed way to reduce Qt3 dependencies is: (drums) PORT YOUR CODE TO Qt4! Qt 4.0 was released almost SEVEN years ago! Yes, Qt 4.0 was released in 2005! Why didn't you (or your dev team) do anything about this in seven years? The Qt3Support module is well documented like most of Qt's libraries. Just use the docs and port everything, class by class.

Related

What is the status of rxandroidble and rxjava2?

I just inherited a project which uses both rxandroidble and rxjava2 (and the associated rxandroid). The previous developer seems to have gotten away with using them together with the versions being just so... But updating any of the related dependencies cause various errors.
Am I correct in assuming rxandroidble is rxjava1 only at this point?
If so, when might there be a version for rxjava2?
Is there a safe (read: stable) way of having both coexist in the same app?
RxAndroidBle is RxJava2 compatible since version 1.5.0 released on 14th of March 2018
Original Answer:
Am I correct in assuming rxandroidble is rxjava1 only at this point?
Yes, current stable release 1.4.3 is RxJava1 only.
If so, when might there be a version for rxjava2?
Soon™.
RxJava2 version is worked on. Current status can be checked in the official Github issue.
Status as of 26th Feb 2018: there is a 1.5.0-SNAPSHOT release that is for RxJava2. (It is in a different namespace than RxJava1 version)
Is there a safe (read: stable) way of having both coexist in the same app?
Assuming you are talking about having RxAndroidBle and RxJava2 and RxAndroid for the same version—yes it should be totally fine to have it in one app. There is also an interop library for chaining both versions of RxJava.

Sharing Qt libraries among Qt applications

Our company ships 2 Qt applications, for now, using Qt5.6 but in some time there will be more (using newer Qt versions). So the problem is, how to make them work all together with different Qt versions? We won't be able to rebuild all Qt apps shipped before, especially if there will be plenty of them. I don't think it's a good idea to place all necessary Qt libraries with each app because the repository size will grow fast. And I think it's just not wise to have many Qt dlls of the same version at one place. As long as I know, .NET solve such problem of different versions with assemblies installer, but I don't think it can help me with Qt. So any ideas of how can I solve it would be highly appreciated. Thanks
UPD: The system is Windows
Actually an answer is quite straightforward, you can ship one Qt version (binaries) as long as they are binary compatible. With each release Qt announce binary compatibility or non-compatibility, so if for whatever reasons you need to switch to newer version and ship new applications with newer not compatible version you might want to ship a new Qt DLL chain.. This can be achived differently (depends on how you layout you install), for example you can have a common lib dir with sub directories based on Qt version which you will extend. (of course you will need appropriate PATHS set then running different applications) :
app\
app\app01
app\app02
...
lib\
lib\Qt5.6.1
lib\Qt5.7.0
etc, then you will have (for example) to wrap your exe files to .bat like:
run.bat
SET PATH=....\lib\Qt5.6.1\
app01.exe
etc..
it's all depends on your install layout and goals

QWebView which version of webkit supported?

I am new to Qt. What I understand is Qt is porting webview from webkit. [Correct me if i am wrong]. and I could not able to find which version of the webkit is ported into Qt 5.0 or higher version.
Kindly suggest me how to find?
It's running on WebKit2, which specific version is a bit more tricky to find out, but you should be able to look through the Qt repository on gitorious to determine it. If I remember rightly it changes depending on how you've built Qt5 and where from.
Seems to be a 3-4 months old snapshot, see the git repo for the included commits.

How to use QtCopyDialog?

I include this library:
#include <QtCopyDialog>
When i compile, i see this error
"QtCopyDialog: No such file or directory"
How to solve this problem?
Thanks.
QtCopyDialog is not part of the core Qt library, but was released as part of Qt Solutions, a now discontinued add-on. The official Qt site links to a newish Git repository containing a few of the original Qt Solutions classes. This appears to be the most (only?) maintained location for the Qt Solutions source, but QtCopyDialog appears not to have made the grade. The only place I can find the source for QtCopyDialog is here. Judging from the docs, the last time it was maintained was pre Qt 4.5. You might need to make some changes in order to get it to work with whatever version of the Qt libs you're using.

Qt3 on Windows?

I need to port one of my old program to Windows. The current version uses Qt 3 on Linux.
I'd like to see it within few days only to do some tests.
Instead of porting my code on Qt 4 (no time now), is it possible to recompile on Windows with Qt 3? Do I also need minGW? Which problems may I have doing this porting?
I can't find Qt 3 for windows, can someone give me a link? or I can use the same qt source I use on Linux?
Yes, you can !
Download the qt-win-3.3.x-8 project on Sourceforge.
QT4 still has back-compatible QT3 classes, prefixed with Q3* (see http://qt-project.org/doc/qt-4.8/qt3support.html)
You should be able to compile & run you QT3 app on QT4 via those classes with minimal adaptations.
Qt-3.2 for Windows was also distributed in a CD bundled with the book "C++ GUI programming with Qt3" at no additional cost with a license for non-commercial use.
ISBN: 978-0131240728
The supported compilers were MSVC and Borland. MingW is not mentioned.

Resources