It would be nice to implement an autoupdater for BaRatinAGE. This means the users can choose to update BaRatinAGE from BaRatinAGE without going through the process of redownloading and unzipping the app. Plus, it should allow for much smaller content to download since the java virtual machin would no longer need to be downloaded each time. How this should be implemented is still unclear and it might be more difficult that I think (or even unfeasible).
In the user perspective, I see three main sub features:
notifing the user that a new version exists:
any time a new release is created, the users get notified upon opening BaRatinAGE
in the help menu, add "check for update button"
download the content of the new version (only what is needed) and replace the corresponding content of the current installed version of BaRatinAGE
restart BaRatinAGE
Here is the outlined on how I think this could be done:
create a seperate small java app responsible for checking on github if another update exists, downloading the new release and replacing the necessary files in the current installation of BaRatinAGE.
any install of BaRatinAGE comes with an app folder. Only the content of this folder needs to be update. This means that any release should also comes with a zip file containing only the content of the app folder so it can be downloaded. The good news is that I think the content is the same for both windows and linux.
add some additional features such as: restart app and load the last loaded project, add a welcome screen that says "thanks for using the last version of BaRatinAGE" with a link to the release note, ...
It would be nice to implement an autoupdater for BaRatinAGE. This means the users can choose to update BaRatinAGE from BaRatinAGE without going through the process of redownloading and unzipping the app. Plus, it should allow for much smaller content to download since the java virtual machin would no longer need to be downloaded each time. How this should be implemented is still unclear and it might be more difficult that I think (or even unfeasible).
In the user perspective, I see three main sub features:
Here is the outlined on how I think this could be done:
appfolder. Only the content of this folder needs to be update. This means that any release should also comes with a zip file containing only the content of theappfolder so it can be downloaded. The good news is that I think the content is the same for both windows and linux.