![]() Each time an installer is built, install4j creates a default updates.xml file in the output directory, and when a new version will be available, I’ll just have to upload that file along with the new version of the installer. The auto-update feature is informed about the availability of a new version thanks to an updates.xml file I’ll have to host at a specified URL. ![]() As I want to provide auto-updating without modifying the Sweet Home 3D source code at this moment, I’m going to set options in install4j that will check if a new version of the program is available when the program is launched. Install4j offers various ways to check whether updates are available and to manage the launching of the updater. Finally, I’ll provide all the nice options that install4j offers for Mac OS X and Linux users by creating a cross platform installer. As install4j includes an auto-update feature, I’m going to use it to update Sweet Home 3D when a new version is released. ![]() But a program lives, and more and more users are used to getting program updates automatically. In the two last articles, I showed how to build an installer with install4j for Sweet Home 3D, then improve it with various options.
0 Comments
Leave a Reply. |