@breezy-kilobyte-39430 any opinions or suggestions on making the loading state of the conversation panel better? PR: https://github.com/OpenHands/OpenHands/pull/12223

yeah let me get you something

would this UI even be possible? If we know the series/types of messages, we probably know the text inside of them

Not sure if I understand the question, it's meant as a loading state for the chat when it is loading a previous conversation.

This is meant to be a replacement to the blue loading spinner that is rendered when waiting to load the WS events. This is part of a series of UI fixes to make the loading states consistent throughout the app (loading skeletons vs spinners). I was thinking of creating a loading skeleton equivalent for some of the different types of components here (messages ad events) and randomize their order / quantity everytime the user is waiting for events to load

We could just animate these, I'm also wondering if we should have it say "loading conversation"

We could just animate these

The PR author has animated them, I think the main problem I find is the solid gray BG for the user message equivalent and the border left of the action title, that mixes both loading state component styles with actual styles. I think if we make them a little more faded and also add the pulsating effect, it'd look OK

I'm also wondering if we should have it say "loading conversation"

We could, but I'd prefer the animated skeletons to make it look a little more dynamic and maintain consistency with other loading states in the app

specifically in your screenshot stephan, it shows a user message with two lines, then an agent message, then two actions when the actual data comes through, it might look very different

This is a better representation of what I am imagining, making it more clear this is a loading state. We can also make it a little less obvious by making it more opaque not to drive too much attention. If this still looks like it'd be jarring, I can get two additional drafts to compare on Friday (the more block-y variant Paul shared and text-only). I opened this issue because I think we can improve our current loading state (second attachement)