Python: Experimental: DevUI Workflow Chat UI #1670
Conversation
…inError 206: The filename or extension is too long
markwallace-microsoft
added
documentation
github-actions
bot
changed the title
Python Test Coverage Report •
Python Unit Test Overview
|
|
Hi @lavaman131 , Thanks for kicking this off. in the mean time, 135 file changes seem on the high side for an additional view. We might need to make significant refactors. |
There was a problem hiding this comment.
Why do we need these .woff and other assets?
There was a problem hiding this comment.
These are used for LaTeX rendering support powered by KaTeX. I'm exploring how to decrease the bundle size.
There was a problem hiding this comment.
I reduced the bundle size by removing this for now since it might not be absolutely necessary.
There was a problem hiding this comment.
I made some optimizations to reduce the bundle size to 1492.01 KB (~1.5 MB). For context, before this change the bundle size was 811KB. If we use gzip compression, we are able to get it down to ~500KB. However, to use gzip compression, we would have to add a middleware that does the de-compression on the client device (more CPU intensive, but minimal overhead and small latency hit the first time a user loads devui).
@victordibia I know you want to keep things slim here, so, let me know what you think makes the most sense. I'm leaning towards the first option for simplicity in the implementation and from my tests locally the loading time was near instant. I might be missing something so feel free to correct me if there's a better strategy.
Alternatively, if agreeable, I could make a follow-up PR with the gzip optimization with the FastAPI middleware.
There was a problem hiding this comment.
Is there duplication of logic as across agent view and workflow view?
Would we benefit from havin ga shared chatinput view across both? or using he exact same view with refactored behviours?
There was a problem hiding this comment.
Great point, unification is possible in theory but might come down to how we represent agents in the core library: Do we want to make agents a wrapper of workflows (agent as a workflow pattern)?
One key difference right now is that the workflow chat is specifically designed to display multiple chat descriptors for each executor id in workflows. For an agent we could potentially have a single chat descriptor for the main agent:
What do you think @victordibia?
There was a problem hiding this comment.
Alternatively, I think it could be possible to make the unification a separate follow-up PR after this gets checked in.
…updated dev dep versions
3 participants
Motivation and Context
Please help reviewers and future users, providing the following information:
Exploration of alternative UIs to represent workflows.
Aiming to improve the UI/UX experience of users working with workflows.
Description
This PR makes enhancements to the workflow UI in DevUI, allowing users to interact with users with a chat-like interface through another collapsible side-panel. See images of UI below.
This pull request improves the usability of the
python/check_md_code_blocks.pyscript by allowing users to specify Markdown files using glob patterns, making it easier to check multiple files at once.Enhancements to file selection:
docs/**/*.md). (python/check_md_code_blocks.py) [1] [2]UI Images