9757760de5
AOT cache (Project Leyden) is built into the installer at packaging
time and dramatically cuts cold-start latency. Three required pieces:
- JDK 25 toolchain for :desktop only — the rest of the project
stays on JDK 21 (JDK 25 runs JDK 21 bytecode, so cross-module
deps still work). Catalog entry named `desktopJvm` to avoid
sharing a prefix with `jvm`, which would otherwise nest the
typed accessor and break `libs.versions.jvm.get()` everywhere.
- `nucleus.aot-runtime` dependency for the `AotRuntime.isTraining()`
detection API.
- `enableAotCache = true` in nativeDistributions.
During the build's training pass Nucleus launches the packaged app
once to record class loading + compilation. The app must self-exit
within 300s or the build hangs; Main.kt now exits immediately if
`AotRuntime.isTraining()`.
Local builds will require JDK 25 on PATH — gradle's toolchain
provisioning should auto-download via Foojay if not present.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .gitHooks | ||
| .github/workflows | ||
| .junie | ||
| .run | ||
| android | ||
| base | ||
| buildSrc | ||
| common | ||
| composeUi | ||
| desktop | ||
| docs | ||
| fastlane | ||
| flatpak | ||
| gradle | ||
| ios | ||
| msix | ||
| readme | ||
| server | ||
| snap | ||
| .editorconfig | ||
| .gitignore | ||
| build.gradle.kts | ||
| CHANGELOG.md | ||
| codecov.yml | ||
| crowdin.yml | ||
| DEVELOPMENT.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| PRIVACY.md | ||
| README.md | ||
| renovate.json | ||
| settings.gradle.kts | ||
Hammer: A story editor
A simple tool for building stories.
Available on:
Take a look at the Roadmap to see whats coming.
Community
Join our Discord and help us by reporting bugs, making feature requests, and discussing the future of Hammer.
Or visit us on Reddit at r/hammereditor
Multi-platform
This app is where ever you are. Your phone, tablet, desktop, laptop, this program can be installed and run, not simply a website-in-a-box, but instead using native client side technologies to provide the best experience possible.
Will add support for more platforms in the future:
Multi-Screen
Whether you are on a phone, tablet, or desktop, Hammer will make the best use of your screen space. Also supporting both light and dark modes.
Offline first
I was frustrated with most of the story writing software I was finding as they were using web technologies (aka: Web Page in a box) which always seems to run into problems while being used offline for long periods of time. Hammer is designed from the ground up to be entirely local, no internet connection required, ever.
Transparent Data
Your data is yours. It's not stored in the cloud, or some opaque database. It is stored in simple, human readable files, just using files and folders to define the project structure. You can open your OSes file browser and take a look for your self. If this program went away today you would be able to easily interact with your data.
Intelligent Syncing between devices
Your data can be synchronized between devices allowing you to work on your story from anywhere, and have no fear of a change on one device, overwriting a change on another device.
Optional and Self hosted Syncing
Syncing is entirely optional, you can install the client and use it on one device, or you can install the server and sync your data between devices. You could even use some other service to sync your data, like Dropbox, Google Drive or syncthing. (however these will only work for syncing between desktop computers. Mobile clients will have to use the built in syncing protocol.)
It's all up to you. Instructions can be found here.
If you don't know how, or just don't want to setup your own server, we're also running an official syncing server.
Official Server: hammer.ink
This is also the best way to support the project! Subscribe to our Patreon in order to get instant access to this official Sync server.
This official server endeavors to be a reliable, and secure way to sync your projects. We perform regular backups, and of course encrypt all of our data both in transit, and at rest in our database. Let us manage the server, and you worry about writing!
Test Environment
We're also running a test environment here: test.hammer.ink which is always running the
latest commit.
Do not use the test environment for real data! It will get cleared from time-to-time without notice!
Development
Want to contribute? Great! Here are some instructions to get you started.
Having a problem?
On desktop, Log are written to:
Windows:
C:\Users\<username>\AppData\Local\DarkrockStudios\hammer\0\logs\
