There are probably more questions to be asked, feel free to edit this description or add them in the comments. Should the composable require an explicit Picasso instance to be passed in, or should we allow one to be provided through a CompositionLocal? This question might not matter depending on the answer to (4).Should we provide error/ placeholder overloads that take composable functions?.should we provide a Composable function that takes all the parameters that can be configured on a RequestCreator, or some way to just provide a RequestCreator to the composable? Since RequestCreator is a mutable, non-compose-stable type, we can’t just pass a RequestCreator instance to a composable function. How much of the existing API should be reused? E.g.Not sure we want to maintain that much code. Accompanist actually provides an internal-only implementation that even supports animated drawables.The simplest thing to do would probably be just host an Android View inside the composition to render drawables.Drawables are not support in Compose, so how should the Compose integration handle them? Some of the Picasso APIs expose drawables.Assuming we want to support it, should it ship as part of the core Picasso artifact or a separate, compose-specific support artifact?.There’s also Kamel which even supports Kotlin multiplatform. Should we even bother? Or just start using Coil instead? Coil is a great library, it provides (nearly all, and even some more) the features of Picasso, it’s extensible, etc.Provide service music: prelude, musical reflection, postlude, hymn/song accompaniment. In coordination with the pastor, provide musical leadership in Sunday worship services (10:00 am 11:15 am). A collection of utilities for Jetpack Compose. Accompanist Image Loading Core Library 3 usages. I don’t have strong opinions on the API yet, but there are some questions that we need to answer: Duties: Accompanist for choir: Work with choir director and choir of 15 people on Thursday evenings 7:00 8:30 pm. A collection of utilities for Jetpack Compose. We still use Picasso heavily internally though, so it might make sense to add Compose support directly to Picasso, at least if it’s not too much trouble. flow, coroutines, accompanist, landscapist, orchestra-balloon, sandwich. The current state-of-the-art for image loading in Compose apps is the Accompanist library, which provides a Compose wrapper around Coil and Glide APIs. 70+ Best Android App Development Projects, Best Jetpack Compose Projects And.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |