<@UH7J3DVPA> No, fxlauncher updates before each st...

# tornadofx

[edvin]

@Stephane M No, fxlauncher updates before each start, no other mode is available as of now :)

[Stephane M]

I see! From a UX perspective that would be a bit annoying for my users. Do you see it being easy to extend this feature as a background task instead, through a library ?

[edvin]

There is already an API available that makes it possible to detect a new version, and it wouldn't be especially hard to add an option to allow the user to skip updating at startup by checking a flag or something like that. The actual download would still have to happen as the app boots, but that shouldn't be an issue. The actual download/update should only take a few seconds, as only your app jar would typically change.

[Stephane M]

I agree with you, unless we start adding / updating dependencies. I think for me the main thing is disabling the checks at boot time, letting the user know of a new version, which triggers a reboot of the app which this time will download the updates. Sounds like the elements are in place, we just need to find how to make them work properly

[edvin]

Yes, I think all we need to change for fxlauncher is for it to read a boolean from somewhere telling it to skip updates for example. This could in your app be false by default, and then you could flip it when you detect a new version.

[edvin]

But maybe you're over estimating how annoying this would be. Your user starts the app, moments later it starts and it is the latest version. I don't really see the issue to be honest.

[edvin]

FXLauncher is already pretty seamless to the end user.

[carlw]

I think you’d want a background service to be running and starting the FX app

[Stephane M]

The problem is that everytime the app starts (at least for me), it displays an "updating" bar, even though there are no updates. And even though it's quick to be gone, it's noticeable