Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 3 months ago
All versions
0.11.3+1.20.2
Beta
[1.20.2] oωo - 0.11.33 years ago 55.3K
Compatibility
Minecraft: Java Edition
1.20.2
Platforms
Fabric
Quilt
Supported environments
Client and server
Changes
Additions
- Multiple tabs can now be selected simultaneously in a single OwoItemGroup (this behavior can be disabled for each group individually if not desired)
- The new
panelWithInset(...)surface allows building interfaces in the style of the Social Interactions screen - Sizing with different methods (for instance, content and fixed sizing) can now be animated between (there are no immediate API changes as a result of this, merely one less runtime warning and a new feature)
- The base point (for layout calculations) and visual position (for rendering and interaction) of an owo-ui cmponent are now two separate concepts (this again comes without any breaking API changes, merely two new methods that should be called in the appropriate places)
- Items can now automatically have their usage statistic tracked by owo through setting
OwoItemSettings#trackUsageStat() - [Experimental] Screens can now implement the
DisposableScreeninterface if they need to be notified when the player actually closes all screens (that is, returns to the game) instead of immediately when navigating to a different screen (which might then later navigate back to the first screen)
Changes
- Methods on owo-ui components which accept a collection of components now use upper-bounded generics instead of an explicit type to allow more specific collections at the call site
Sizing.fill()can now be called with zero arguments to indicate 100% fillUIParsing.registerFactory(...)can and should now be called with an indentifier instead of a plain string for the element nameParentComponent#childById(...)is no longer @Nullable, as it is generally expected to return a component in its most common use-case (querying the constituents of a UI model)
Fixes
- Trimmed armor in an ItemComponent now renders properly (#152, Zailer43)
- Explicitly positioned owo-ui components are no longer inflated twice for each single layout pass
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ccKDOlHs:oLoJCrky"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccKDOlHs:oLoJCrky"
}

