ViewPropertyObjectAnimator
kotlin-result
Our great sponsors
ViewPropertyObjectAnimator | kotlin-result | |
---|---|---|
11 | 33 | |
338 | 934 | |
- | - | |
2.5 | 8.9 | |
9 months ago | 8 days ago | |
Java | Kotlin | |
Apache License 2.0 | ISC License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ViewPropertyObjectAnimator
-
Am i safe by sticking with Java and XML for years ahead ?
I've been using https://github.com/blipinsk/ViewPropertyObjectAnimator and it's amazing
-
intuitive jetpack compose animations
you just use https://github.com/blipinsk/ViewPropertyObjectAnimator for everything, and if you need shared element transtiions you cry (then again, it's not like Compost can do that at all, so)
- Adding animation to recyclerView in an MVVM app requires a lot of boilerplate code
-
Why is Compose better than XML in your expirence? I'm preparing a post looking at TRUE benefits. Input appreciated.
Animations with views were much easier, you just had to use this lib https://github.com/blipinsk/ViewPropertyObjectAnimator and animator sets made it trivial. If you needed fancy crossfades then TransitionManager.beginDelayedTransition(container) and that's it.
-
What is actually the right way to make an android app?
Honestly, they're pretty even in that regard. Whether you use XML or Compose in "simple apps" is up to you. Some things are easier in Compose, and some things are just stupid tricky. Animations in Compose are the worst imo, with ViewPropertyObjectAnimator they used to be trivial for XML layouts.
-
4 reasons Jetpack Compose is better than XML
This is probably just my experience, but with Compose I have to muck around with LaunchedEffects and manual interpolation, while with XML views I could just use https://github.com/blipinsk/ViewPropertyObjectAnimator and AnimatorSet().playTogether().
-
Can someone review my coding assignment for a job? How valid is the feedback from the engineers who reviewed it?
That, and animations with https://github.com/blipinsk/ViewPropertyObjectAnimator were much easier than linear interpolating in a LaunchedEffect, and shadow support is basically non-existent (Modifier.shadow() doesn't work as you expect, even android:elevation was better).
-
Is it okay to set margin values to negative?
I like this library https://github.com/blipinsk/ViewPropertyObjectAnimator
-
What are the most underrated third party libraries for Native Android?
I don't know how to write animations without ViewPropertyObjectAnimator https://github.com/blipinsk/ViewPropertyObjectAnimator
-
Compose stable coming in July
Really? I just used https://github.com/blipinsk/ViewPropertyObjectAnimator + AnimatorSet for everything and it always just worked
kotlin-result
-
How do you define errors?
Sealed classes in combination with a library like https://github.com/michaelbull/kotlin-result will get you what you need. Essentially at that point you'll be doing error handling the way you would in Rust, where a 1-level deep sealed class containing data classes as children act as the root error type and each of its variants. If you have errors coming from two different domains you just create a wrapper error type for each domain.
-
Result Class with Generic Type for both Success and Failure States
This is a great result lib: https://github.com/michaelbull/kotlin-result
-
Is runCatching in use in any of your projects ? My team is abusing it
Lastly I do not like kotlin's Result and we use the kotlin-result library which is more expressive and not tied to Throwable (similar to Arrow's Either).
-
Struggling with software robustness with Kotlin
In my own code, I started to use explicit error handling. I'm currently experimenting with Result (from https://github.com/michaelbull/kotlin-result) and Raise (from https://arrow-kt.io/).
-
Thoughts on Kotlin Multiplatform?
un-related to multiplatform i've found it extremely helpful to wrap things in a Result type. If something can throw an error, it get's a Result return type. It sounds like that would help your use case too. The built in Result may be useful too
-
Programming with Result
This is a better impl.
- It seems like I'm forced to make this choice at least once a day
-
Are nearly all your functions suspend?
Using a result type can help to differentiate quite nicely. https://github.com/michaelbull/kotlin-result
-
Kotlin Nitpicks: Language and Standard Library
kotlin-result
- Almost Everything I've Learned About Error Handling in Kotlin
What are some alternatives?
ArcAnimator - ArcAnimator helps to create arc transition animation: 2.3.+
result4k
AnimationEasingFunctions - Android Animation Easing Functions. Let's make animation more real!
kotlin-monads - Monads for Kotlin
Lottie for Android, iOS, and React Native - Render After Effects animations natively on Android and iOS, Web, and React Native
Result - The modelling for success/failure of operations in Kotlin and KMM (Kotlin Multiplatform Mobile)
UltimateAndroidReference - :rocket: Ultimate Android Reference - Your Road to Become a Better Android Developer
Arrow Meta - Functional companion to Kotlin's Compiler
CircleIndicator - A lightweight indicator like in nexus 5 launcher
Komprehensions - Do comprehensions for Kotlin and 3rd party libraries [STABLE]
AndroidViewAnimations - Cute view animation collection.
Kategory - Λrrow - Functional companion to Kotlin's Standard Library