Philip Meier

> I'm a dinosaur That could go at least two routes: 1. "This is what we used back in my days. Not sure what is happening today" 2. "Trust me,...

One thing that I want to avoid, is to come up with a customization scheme that does not support common cases. One thing that I have seen a lot in...

Ok, let's just roll with CLF for now and worry about this later. I prefer to make this configurable by the user, but having a more reasonable by default is...

Let's do a two-step approach here: 1. Upgrade our requirement to `panel==1.4.0` just making sure that everything that worked before still works. 2. Check out the improvements that came with...

Testing locally, I noticed two differences: ## Loading indicator https://github.com/Quansight/ragna/assets/6849766/c04bc477-deeb-43c0-8ccd-afbbe85c4495 https://github.com/Quansight/ragna/assets/6849766/5050e055-9ac4-43fc-b29f-8c7b4edd713d ## Accordion rendering   Since both things are purely styling, I'm also ok to just merge...

> Remove chat_document_pills from header That is not going to happen. Having the documents used for the chat visible by default is intended. Instead what we should do in this...

> post some of his insights into the performance of Ragna's UI in the discussion section sometime this week. Those insights might be helpful in making sure the UI stays...

We also need some handling for the popup:  Here we shouldn't truncate, but rather provide a scrollable view.

I've added a hard limit for 20 visible documents in #235. This doesn't solve any of the graphics issues raised here, but at least prevents performance hits when one is...

The code on the UI side to parse the schema could look like ```python from panel.widgets import EditableIntSlider from ragna.assistants import Gpt35Turbo16k def make_panel_widgets(schema): widgets = {} for name, parameter...