fxlauncher | Auto updating launcher for JavaFX Applications

by edvin Java Version: v1.0.21 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | fxlauncher Summary

fxlauncher is a Java library typically used in User Interface, Electron, Gradle, JavaFX applications. fxlauncher has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

Auto updating launcher for JavaFX Applications. Combined with JavaFX native packaging, you get a native installer with automatic app updates. You can see the launcher in action in this Demo Application.

Support

Quality

Security

License

Reuse

Support

fxlauncher has a low active ecosystem.

It has 632 star(s) with 90 fork(s). There are 48 watchers for this library.

It had no major release in the last 12 months.

There are 51 open issues and 114 have been closed. On average issues are closed in 64 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of fxlauncher is v1.0.21

Quality

fxlauncher has 0 bugs and 0 code smells.

Security

fxlauncher has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fxlauncher code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fxlauncher is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

fxlauncher releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 1168 lines of code, 82 functions and 14 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed fxlauncher and discovered the below as its top functions. This is intended to give you an instant insight into fxlauncher implemented functionality, and help decide if they suit your requirements.

The main entry point
Resolves the cache directory
Checks if files are newer
Sync the manifest
Initializes the Stage
Run the specified Runnable on the JavaFX thread
Launch application from manifest manifest
Initialize the application
Entry point to the launcher
Creates a Manifest from an application path
Creates the loader
Compares two library files
Creates and returns a new updatedater
Build an array of classpath
Builds a hash code for this element
Creates a hash code

Get all kandi verified functions for this library.

fxlauncher Key Features

No Key Features are available at this moment for fxlauncher.

fxlauncher Examples and Code Snippets

No Code Snippets are available at this moment for fxlauncher.

Community Discussions

Trending Discussions on fxlauncher

How to update native built JavaFX Application

How to access previous app state/config on app relaunch (TornadoFx)

QUESTION

How to update native built JavaFX Application

Asked 2019-Apr-04 at 14:23

I am building a JavaFX application in Intellij that will be built and distributed with an .exe installer and will be ran as an exe Application. I have been trying to find a way to allow for remote updates, but I have only found resources that update a jar file by using another jar file hosted on a website. Is there a way to allow for remote updates to a exe JavaFX application? I have though about using update4J, but sadly I have no idea how to implement it, use it, or if it will even work with exe applications. I have tried to use FXLauncher, but I am not able to use JavaFX with maven as an error occurs whenever I try adding maven framework to the project.

...

ANSWER

Answered 2019-Apr-04 at 14:23

I am the developer of update4j.

The framework used to be complex and hard to use, but the last release (1.2.2 at time of writing) significantly simplified things leaving only one pain point, namely, generating a configuration.

So for starters, launch the framework using it's own main method:

Source https://stackoverflow.com/questions/52393968

QUESTION

How to access previous app state/config on app relaunch (TornadoFx)

Asked 2018-Jul-27 at 20:58

After looking at state/settings, configuration, I have tried config and app.config for app state/setting management. When I use app.config, I am able to access the state in other views.

I wish to implement state such that when the app is launched a second time, the first view or behavior should be different based on the state config/settings of the previous session.

I realized that each time I relaunch the app all states default to null.

I even came across the notion of configBasedPath and configPath but what I am not sure about is,

if my app is to create them automatically or I need to do it manually
If my app will automatically resolve the config path to app.properties or I will need to do it manually.

This is because after running my app, I do not see the default conf base directory and the app.properties file.

I am currently developing on windows 10 and use FXLauncher for packaging.

How can I persist state in my app such that I can always access the previous states/settings I run the app?

...

ANSWER

Answered 2018-Jul-27 at 20:58

To persist configuration changes, simply call save() on the config object. To save the global app config settings, call app.config.save(). Changes are automatically loaded when the app starts.

You can read more about the config object in the guide:

https://github.com/edvin/tornadofx-guide/blob/master/part2/Config%20Settings%20and%20State.md

Source https://stackoverflow.com/questions/51564522

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fxlauncher

Maven Example with pom.xml
Gradle Example with build.gradle
It's worth noting that the two package alternatives for Windows, (EXE and MSI) have different default install locations. While EXE will default to %LocalAppData%, the MSI installer will default to %ProgramFiles%. To write to %ProgramFiles% one definitely does need admin privileges—that poses a problem for FXLauncher which, by default, downloads updates to where it was installed. If you use the MSI installer you will therefore need to tell FXLauncher to cache artifacts somewhere it is allowed to put them. For an OS-independent answer to this problem, look no further than the two magical strings, USERLIB and ALLUSERS.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: