Supports Qt's Event Loop.
Supports Qt's Event Loop.
QInstallerBridge fully supports Qt Projects by flowing with its event loop and thus you will have no problem integrating QInstallerBridge with your Qt Project.
Does not depend on Qt Installer Framework
Does not depend on Qt Installer Framework
Whether you are Updating or checking for Updates QInstallerBridge does not need Qt Installer Framework , (i.e) The Maintainance Tool for anything and thus makes QInstallerBridge work on its own and also flowing with the Maintainance Tool.
Only Requires Configuration!
Only Requires Configuration!
QInstallerBridge only operates with the configuration files generated by Qt Installer Framework and this is only used to communicate with the Maintainance Tool to let it know about the newly installed update , to avoid re-update!
Header only library!
Header only library!
QInstallerBridge does not like leaving heavy traces for the users and thus it is packed with all its amazing features in a single C++ header file , this makes QInstallerBridge easier to integrate with your project.
Clean C++ API.
and thus integrating this header will not affect your source , So this project is also
best suited for those who care about code taste.
Why Create QInstallerBridge ?
Why Create QInstallerBridge ?
Ever wanted to make your applications work with the flow but stuck with Qt's Maintanance Tool.I belive that updates should be just installed without any complications but that does not mean Qt Installer Framework is a bluff , its actually the coolest thing a vendor can have. With Qt's Installer Framework you can ship your packages to Linux , Windows and Mac with a cross-platform gui installer but the one thing that sucks is that Qt does not provide a auto update officially but it does have theMaintanance Tool which can auto update. Some cool folks used QProcess to communicate with the Maintanance Tool and that did work as a hotfix but I needed a solid and clean API to communicate with Qt's Maintanance Tool and thus QInstallerBridge was born.
