From adebf080cbb218fcea9db37567e59ab6b3b98f4f Mon Sep 17 00:00:00 2001 From: skydoves Date: Wed, 6 Nov 2024 14:12:12 +0900 Subject: [PATCH] Improve README --- README.md | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index f2aed00..a0319d6 100644 --- a/README.md +++ b/README.md @@ -36,32 +36,24 @@ dependencies { } ``` -### SNAPSHOT -[![Bindables](https://img.shields.io/static/v1?label=snapshot&message=bindables&logo=apache%20maven&color=C71A36)](https://oss.sonatype.org/content/repositories/snapshots/com/github/skydoves/bindables/)
-Snapshots of the current development version of Bindables are available, which track [the latest versions](https://oss.sonatype.org/content/repositories/snapshots/com/github/skydoves/bindables/). -```Gradle -repositories { - maven { url "https://oss.sonatype.org/content/repositories/snapshots/" } -} -``` - ## Setup DataBinding If you already use `DataBinding` in your project, you can skip this step. Add below on your `build.gradle` and make sure to use `DataBinding` in your project. ```gradle plugins { - ... - id 'kotlin-kapt' + .. + id('kotlin-kapt') } android { - ... + .. buildFeatures { - dataBinding true + dataBinding = true } } ``` ## BindingActivity + `BindingActivity` is a base class for Activities that wish to bind content layout with `DataBindingUtil`. It provides a `binding` property that extends `ViewDataBinding` from abstract information. The `binding` property will be initialized lazily but ensures to be initialized before being called `super.onCreate` in Activities. So we don't need to inflate layouts, setContentView, and initialize a binding property manually. ```kotlin