You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe a crazy idea but... many of our samples currently include a html+javascript+websocket based chat UI (almost exactly the same in all cases). It sounds like we could extract that into something that applications can easily import, either as a separate extension, or a capability of the core extension, and offer some simple SPI to allow applications to customize it.
Compared to the chat page in Dev UI, this would also be available in prod mode.
The text was updated successfully, but these errors were encountered:
I would expect people to want a UI that use their JS framework (Vue, React...) and styling conventions (CSS framework) so that might be hard to consume by end users.
Yeah that certainly is true, but maybe for enabling some quick projects, and demos, a built-in solution that offers just 'enough' customizability may be good. I don't know.
The sole fact that like 6 of our sample projects duplicate several large html/js files is something to think about. And the same is also in the workshop (https://quarkus.io/quarkus-workshop-langchain4j/), and we expect the users to download a prepared project rather than create it from scratch, which isn't that nice either.
Maybe a crazy idea but... many of our samples currently include a html+javascript+websocket based chat UI (almost exactly the same in all cases). It sounds like we could extract that into something that applications can easily import, either as a separate extension, or a capability of the
core
extension, and offer some simple SPI to allow applications to customize it.Compared to the chat page in Dev UI, this would also be available in prod mode.
The text was updated successfully, but these errors were encountered: