QDjango alternatives and similar libraries
Based on the "Web Application Framework" category.
Alternatively, view QDjango alternatives based on common mentions on social networks and blogs.
8.6 9.0 QDjango VS drogonDrogon: A C++14/17 based HTTP web application framework running on Linux/macOS/Unix/Windows [Moved to: https://github.com/drogonframework/drogon]
8.3 7.9 QDjango VS Oat++🌱Light and powerful C++ web framework for highly scalable and resource-efficient web application. It's zero-dependency and easy-portable.
5.1 8.1 QDjango VS CutelystA C++ Web Framework built on top of Qt, using the simple approach of Catalyst (Perl) framework.
3.1 0.2 QDjango VS QSimpleScadaQt based simple SCADA framework, with dashboard, static and dynamic components
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of QDjango or a related project?
QDjango - a Qt-based C++ web framework
Copyright (c) 2010-2015 Jeremy Lainé
QDjango is a web framework written in C++ and built on top of the Qt library. Where possible it tries to follow django's API, hence its name.
It is released under the terms of the GNU Lesser General Public License, version 2.1 or later.
To learn more about QDjango, please read the online documentation.
QDjango builds and is auto-tested both with Qt 4 and Qt 5.
Qt 4 on Debian:
sudo apt-get install libqt4-dev
Qt 5 on Debian:
sudo apt-get install qtbase5-dev
Qt 4 on Mac OS X:
sudo port install qt4-mac
mkdir build cd build qmake .. make
You can pass the following arguments to qmake:
PREFIX=<prefix> to change the install prefix default: unix: /usr/local on unix other: $$[QT_INSTALL_PREFIX] QDJANGO_LIBRARY_TYPE=staticlib to build a static version of QDjango
If you wish to discuss QDjango, you are welcome to join the QDjango group.
Fast forward cursors are used by default. This greatly improves performance, and has the added benefit of implicitly converting to a static cursor when it needs to. Unfortunately, this also means that these cursors can block a connection to the server. In order to deal properly with this situation, there are a few requirements:
- Connection pooling must be enabled in your ODBC manager
- You must enable Multiple Active Result Sets in the QODBC driver using "MARS_Connection=Yes" in the connection string
- You must enable connection pooling in the QODBC driver using the "SQL_ATTR_CONNECTION_POOLING" attribute
*Note that all licence references and agreements mentioned in the QDjango README section above are relevant to that project's source code only.