Hi, I have a few questions about Google’s Remote C...
# compose
g
Hi, I have a few questions about Google’s Remote Compose. 1) Is it currently possible on the server side to create a component (for example, a custom button) and use it inside other server-side components, so that the client downloads binaries like this: - custom-btn.rcb - card1.rcb - card2.rcb And then, if a new component is added that uses that button, the client wouldn’t need to download the button’s binary again? 2) My next question: does the current capability allow us to define a node on the server with a set of parameters (e.g., inside a remoteColumn), and then register that component on the client as a native component—for example, for rendering a map, a video player, or a Coil image?
@Nicolas Roard
y
No. It's currently a single doc. Nico might have a newer answer with some of the macro changes.
n
The new template engine will allow this type of usage (referencing a component separately), but out of the box this isn't yet supported in the androidx player.
for #2 I have a CL I need to resurrect to support "custom components" like that where the player can provides a native component, so it's planned, just will take a bit to land as other things take precedence
❤️ 2
g
I’m also curious about how to implement a TextField in Remote Compose, given that it’s not yet implemented.
@Nicolas Roard
y
I don't think we have any events for text input. And it's not really in the current scope. Ideally to support we have it as a custom component, so you just get the platform component android Or compose BTF. But implementing from scratch is a bad idea
👍 1
n
yep the current aim is more about delivering flexible content. In the short term the easiest way to add textfield support will be when I add the host custom components path I mentioned above, medium term we might surface something more built-in.