The launcher for BlueMaxima's Flashpoint (the web preservation project).
- BlueMaxima's Flashpoint - Download Flashpoint here (the launcher is bundled with it)
- Trello - Upcoming features, known bugs etc.
- Launcher Releases - Download release builds of the launcher here
The Flashpoint Launcher (FPL) is a desktop application made for browsing, storing and launching other applications (games, animations, web apps etc.). It is specifically made for BlueMaxima's Flashpoint, which is a web preservation project.
docs folder for more information on setting up Flashpoint and Extension authoring.
Extension API Documentation: https://flashpointproject.github.io/launcher_ApiDocs/
Building from source
- Git (for downloading and updating the source code and sub-modules)
- Node & NPM (for building and running the source code)
Follow Development Setup, using
master branch for a stable release or
develop for the latest features. After setup is complete, run
npm run release to generate release builds in
Install by running
sudo apt install libgtk-3-0 libnss3
Clone the repository with
git clone --branch develop --recurse-submodules https://github.com/FlashpointProject/launcher.git launcher(where
launcheris the path of the directory you want to be the root of the repository).
Navigate to the root of the repository and run
npm install- this will download and install all the dependencies from npm (it may take a few minutes).
npm run buildor
npm run watch(at the root of the repository). This will compile the source code and such so the launcher can be executed. If
watchis used, it will rebuild the launcher automatically when a source code or static file is changed.
npm run start(at the root of the repository) to start the launcher. It is recommended to do this in a second command prompt / terminal.
Optional - It is highly recommended to set the launcher's "Flashpoint folder". This is where the launcher will read and write most data to and from. You can set the "Flashpoint folder" path at the "Config" tab in the launcher. Make sure the background of the text field is green (this means the path is valid) and don't forget to hit "Save and Exit"!
- You will need to run
npm installwhenever a dependency is added or upgraded in
- The launcher is changing rapidly and does not always support older "Flashpoint folders". Sometimes it does not even support the most recent one.
- It is recommended to have a separate "Flashpoint folder" for launcher development than normal usage.
Short descriptions of what the scripts in
build- Build the launcher (build main & renderer and copy static files to
watch- Build the launcher and incrementally rebuild it when the source or static files change
pack- Pack the latest build (and put the packaged file with the executable electron app in
snapshot- Build then pack the launcher (same as running
release- Build then pack the launcher in release mode (same as
snapshotbut it also creates installers, build artifacts etc.)
start- Run the latest build of the launcher
test- Run the test suite (to find out if anything covered by the tests has been broken)
lint- Run the linter
release will by default pack for the OS and architecture of the machine that runs it.
To pack for a specific OS / architecture use the handy package scripts (such as
release:win32) or set the environment variables
"Not allowed to load local resource" Error
If this error appears in the electron applications console, it is probably because the file it is looking for does not exist. To solve this, run
npm run build
Not allowed to load local resource: file:///<ProjectPath>/build/renderer/index.html