Pedro Gomez05/22/2019, 6:38 AM
However, this is not part of the repository right now and we will have to wait until a new release in order to check if the suggested implementation looks like this or not.If nobody documents how the library is implemented the only thing I can find is questions around. I'm not judging anybody. I'm really sorry if you or your team feel bad because of my blog post. I didn't mean to hurt you or your team feelings. I already told Adam and the whole team I think you are doing it great with compose and as I said in my blog post:
The Android team is doing it great. Believe me when I say that this Compose API is way better than the current state of the art of Android development.During the Google IO talk the team said "go to the repo and play with compose" and that's what I did. After playing with compose and the available documentation I wrote the post. if compose has an API that is not documented or used in the example provided, I'm afraid I can't review it. If you have examples of things that don't match what I explained in the blog post I'll add a note with the resources you provide me. I hope these resources will be part of the documentation soon.
romainguy05/22/2019, 6:01 PM
Pedro Gomez05/22/2019, 7:29 PM
I guess there is an inner mechanism inside the rendering code making all these components efficient when talking about drawing. However, I can't talk about it because it wasn't part of the talk and the code I've reviewed seems to use canvas API for the component's rendering.I've updated that paragraph to express better this will depend on the final implementation
Sean McQuillan [G]05/23/2019, 4:08 PM
Pedro Gomez05/23/2019, 7:58 PM