antony-jr/qinstallerbridge

:roller_coaster: A small header writen in C++ using Qt5 to :computer: communicate with the Qt Installer Framework :eyeglasses: . This header helps you to check the remote repo :white_check_mark: and also update to the latest version! :dog:

🎢 A small header writen in C++ using Qt5 to 💻 communicate with the Qt Installer Framework 👓 . This header helps you
to check the remote repo ✅ and also update to the latest version! 🐶
--Antony Jr.

Important: I made this for prototyping a long time ago and thus the code is very inefficient , the rewrite of this library is taking place in the experimental branch which should take a while to merge into master so please sit tight.

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 the
Maintanance 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.

QInstallerBridge is a small header writen in C++ using Qt5 , This supports async structure and thus it is best suited
for your Qt Projects. QInstallerBridge does not depend on Qt's Maintanance Tool , it just works on its own and
handles Qt's Remote Repo very well. It also communicates with the Maintanance Tool's configuration to make the
Maintanance Tool know that we have updated to the latest version.
This makes QInstallerBridge to act without Maintanance Tool and also flows with it!

You can also just distribute your app with components.xml to use QtInstallerBridge without the Qt Installer Framework Cool , Right ?...

Note : Eventhough you do not need to install your packages with Qt Installer Framework , you need Qt' Remote Repo.
Which is generated with repogen from the Qt Installer Framework.

Warning : The components.xml should match the configuration with Qt's Remote Repo's Updates.xml.
That is common sense , right ?...

Please refer the documentation for more information. Open issues if you have any doubts , I will gladly answer you ❤️ !

Some Cool Folks who use QProcess to Auto Update

• Skycoder42
• Jordanbaucke
• A StackOverflow that roots for QProcess

Some Similar Projects

• AutoUpdater-Qt by speedovation

Getting Started

Learn more about QInstallerBridge at the official QInstallerBridge Documentation

Thank You

I really need to thank the developers of this libraries for creating it because QInstallerBridge is elegant because of them! ❤️

• QArchive
• QEasyDownloader
• Qt

Support

If you think that this project is cool then you can give it a ⭐ or 🍴 it if you want to improve it with me. I really ❤️ stars though!

If you want to do something that stands out then you can click the donate button at the top to make a monthly donation , So
I will make sure that I stay healthy and keep on to do my work. 💼 Supporting me means supporting all of my projects , So
you are like Tony Stark ❤️ who backs Spider-Man! Thank you for your extra care! 🐶

You can also tweet about me on twitter , get connected with me @antonyjr0

Thank You! 😺

License

The BSD 3-clause "New" or "Revised" License.

Copyright (C) 2017 , antony jr.
All Rights Reserved.

qinstallerbridge's Issues

Support for component scripting (and checksums)

• Bug
• Question
• Suggestion
• Other (please describe):

QtIFW allows you to embbed javascript files for component scripting to for example create shortcuts or provide custom user interfaces. I don't see any of this (as well as other meta-stuff, like verifiying checksums) in your library. Are there any plans for supporting these additional features of QtIFW.

Note: I think at least verifying the checksums is a must. You can use QCryptopgraphicHash for that.

You can read more about component scripting here: https://doc.qt.io/qtinstallerframework/scripting.html