rio-labs
[Feature Request] compatibility with gradio custom components
Description
Hi.
Gradio is a prominent python webui framework with definitevely an overlapping use case with rio. Gradio also supports custom components.
Suggested Solution
I think it would be a smart move from rio to either be able to turn a rio component into a gradio custom component OR to use gradio component inside rio.
Alternatives
No response
Additional Context
No response
Related Issues/Pull Requests
No response
This looks interesting and could be worthwile if Gradio's paradim is close enough to Rio's. We'll have to discuss this after reading into their component system.
There's one obvious question that pops up in my mind: If somebody wants to use Gradio, why would they be using Rio. Likewise, if somebody is using Rio, why would they want to also use Gradio. I guess the real benefit here is that any basic components could be shared between the two?
Glad you keep an open mind.
Off the top of my head:
- Gradio recently unveiled their custom component system. I see some popping up here and there and rio would benefit from deduplicating efforts. Things like "wow now LLM are completely multimodal, how can I make the chatbot UI make use of this".
- I can see people prefering rio's syntax.
- ~~It seems a lot easier to create custom component for rio than gradio.~~
I've recently been looking at Gradio, and it transpires that all of their components are available in Javascript.
