Search Results for "java runtime"

cpu_features is a cross-platform C library developed by Google that provides a simple and efficient way to detect available CPU features at runtime across a wide range of architectures and operating systems. It enables applications to determine which instruction sets (such as SSE, AVX, or NEON) are supported on the host machine, allowing developers to optimize performance dynamically. The library supports numerous architectures—including x86, ARM, AArch64, MIPS, POWER, RISCV, LoongArch, and...

Hoplite is a Kotlin library for loading configuration files into typesafe classes in a boilerplate-free way. Define your config using Kotlin data classes, and at startup Hoplite will read from one or more config files, mapping the values in those files into your config classes. Any missing values, or values that cannot be converted into the required type will cause the config to fail with detailed error messages.

This library allows the usage of RxJava with the new Android M permission model. If you need to trigger the permission request from a specific event, you need to setup your event as an observable inside an initialization phase. You can use JakeWharton/RxBinding to turn your view to an observable (not included in the library). Because your app may be restarted during the permission request, the request must be done during an initialization phase. This may be Activity.onCreate, or...

Colorful is an Android library aimed at simplifying the use of color and theme customization in Android applications by providing utilities for generating, manipulating, and applying dynamic color schemes at runtime. It abstracts away the complexity of Android’s standard theming system and gives developers a higher-level API for tasks such as tinting UI components, generating complementary color palettes, and producing visually consistent themes based on a primary color. With Colorful, you...

ButterKnife is an annotation-based view binding library for Android that reduces boilerplate in Activities, Fragments, and custom views. Developers replace repetitive findViewById calls with BindView fields and define UI event handlers using annotations like @OnClick, with the library generating efficient binding code at compile time. Because it relies on annotation processing, there’s no reflection at runtime, keeping startup paths lean and predictable. The generated bind/unbind lifecycle...