power-adapters
power-adapters copied to clipboard
NextFaze
Composable adapters for Android RecyclerViews and ListViews
Add a way of accessing the absolute position of the element in the adapter. This way, the position can be compared against the root container size, and different binding logic...
Use the `@CheckResult` in the Kotlin adapter builder DSL, which will hopefully flag the common user error where one forgets to use `+`.
Due to the recent layout resource optimization, where 2 `Binder`s shared an item type automatically if they used the same layout resource, binders must reset all aspects of the view...
After recent changes, we now use an `ExecutorService` in `ArrayData`, etc. We should also use `DiffUtil` to emit precise change notifications, running the diff in a worker thread.
For some applications, having stable item IDs is necessary. Currently if a PowerAdapter with stable IDs is composed with a `ViewFactory` or `varargs layoutResources`, it'll lose its stable item IDs...
Item IDs have a problem, which is ensuring composed adapters with stable item IDs form a composite adapter whose ID ranges don't accidentally overlap. If they overlapped it'd result in...
This allows subclasses of RecyclerConverterAdapter to also use their own subclasses of RecyclerConverterAdapter.ViewHolder. This enables the use of AdvancedRecyclerView's (https://github.com/h6ah4i/android-advancedrecyclerview) drag-and-drop, which requires that ViewHolders implement a certain interface.
As per #46, it'd good to allow subclassing the `ViewHolder` as well as the adapter class itself, for interoperability with other adapter libs.
Add the ability to specify 0+ `ItemDecoration`s on a `PowerAdapter`: * Add item decoration methods to `PowerAdapter` * Apply the existing nesting logic when invoking the decoration methods This would...
Support the change payload stuff now available with `RecyclerView` adapters: notifyChanged(Object payload)