Why it exists
Software used to look like it was made of something. This is that look as a working library: thick glossy frames, dark bodies with a soft glow, chrome orb buttons, LCD readouts, XP tray balloons, around a single toxic lime accent, in three skins called Toxic, Media and Crystal.
Every component, held by pixels
All 51 components of the design system are built, with the nine pages of its demo as the sample app. Each is held to the design by pixel parity against references rendered from the design system itself in headless Chrome, and the floor of that comparison was measured once rather than chosen.
Tokens are generated from the design system's file, so a component holds no literal colour, size or duration of its own, and the public API is pinned by a committed dump that fails the build when it moves without being recorded.
Text at 200 %
Sizes are in sp, so the type scales with the system's font setting. The design system has a stress page for exactly that, and it is one of the sample's nine pages. Press the switch in the demo above.
In an application
kachok, a BitTorrent client for the desktop, offers oldge-ui as one of its two interface kits, in any of the three skins. Many of the kit's issues were filed from it, by a window that needed the component.
Install
repositories {
maven("https://reposilite.kotlin.website/snapshots") {
mavenContent { includeGroupAndSubgroups("io.github.youndie") }
}
}
dependencies {
implementation("io.github.youndie:oldge-core:0.1.1.<build>")
}
Every build of main publishes a version, and the latest is the last one in maven-metadata.xml.
OldgeTheme(OldgeSkin.Toxic) {
OldgeScreenBody {
OldgeButton("Войти", onClick = {}, variant = OldgeButtonVariant.Primary)
}
}
Targets: desktop (JVM), Android, iOS and wasm. Apache 2.0; the bundled fonts keep their own licences.