Releases: averyocean65/swp
SWP Update - Version 1.0.1
This update of SWP brings some bugfixes and QoL updates that are sure to make the program easier to use.
Patchnotes
Features
Save As
In SWP there's now the ability to use the "Save As" operation for saving files, this allows the user to save any existing file in a separate location, an essential feature of text editors that we sadly overlooked in the last release.
Changes
- The name of the file saving error dialog was changed to be easier to understand.
- Menu item names were changed (i.e. "New File" is now "New")
- Version update was changed in the SWP Information Window
Bugfixes
- SWP now automatically creates required files when you save.
- SWP doesn't add a newline at the end of the text area when loading a file anymore.
How do I run SWP?
To see how to run SWP, please check out the project README
We hope you enjoy this new version of SWP!
First version of SWP!
The first version of SWP is here! With it you can quickly and easily create, open and save files without much hazzle.
We hope you enjoy it!!
Prerequisites
In order to run SWP you need to have a Java Development Kit of version 11 or above, as well as a Java Runtime Environment, else the program simply won't run.
How to run
Windows
Context Menu / Double Click
Providing that you have Java 11 (or over) installed on your system, make sure to run the provided .jar file with the installed Java(TM) Platform SE Binary.
run.bat File
You can use the provided batch file to run SWP, so long as the batch file is in the same directory as the .jar file.
Terminal
Run java.exe -jar SWP.jar to run SWP.
Linux
Shell script
Ensure that the script is executable, by either checking the permissions or using chmod +x run.sh (or similar) to set the script to be runnable.
You can use the provided shell script file to run SWP, so long as the shell script file is in the same directory as the .jar file..
Terminal
Run java -jar SWP.jar to run SWP.
What about an .exe or app image file?
We don't provide .exe or Linux app image files for this project, because it uses Java. Packaging the application in a OS-specific format defeats the purpose of Java and the JVM, as .jar files are meant to be platform independent executables and libraries. We also tried using tools to convert the .jar files to executables, but found the results either extremely unstable or unusable no matter how we configured the tool.