Howdy everyone! I'm <Dev> and here's some screensh...
# share-your-work
d
Howdy everyone! I'm Dev and here's some screenshots from my malleable developer environment
desh
• it's meant to be usable by humans without agents while also being a nice place for agents • all those contextual actions are partially inspired by hypermedia concepts, and are exposed to agents too, and are one way it can modify itself at runtime / enable end user programming • it can work with voice, touch, etc. lots more features but curious to hear questions and feedback while I work on a video
❤️ 2
(screenshots best viewed in file name / chronological order, which I think slack reverses)
quick video in case the screenshot ordering is confusing
it's multiplayer by default, and everything is tracked / has provenance by default
m
I really like the idea that data can be viewed in multiple editors. I wonder what kind of UI primitive could represent this idea best... Patchwork uses "Open with..." select box in the tool bar (low visual noise, very clear, but slow to switch). Desh seems to have pill-shaped tabs (more noisy, less clear, but very fast to switch between editors). Clarity could be improved with some text or tweaked visuals. What's also nice about Desh's UI is a clear hierarchical structure. You can go top-down: WORKSPACE => resource name => editor selection => editor body => editor options. I feel like this is the right shape for multi-editor UI.
❤️ 3
d
Definitely agree there's plenty of room to improve on desh ui. The contextual actions/editors/viewers are populated based on path, file extension, other hints, and contextual state from e.g. navigating the UI. The primary user is the agent who has access to the same capability. That makes it easier for them to only use valid tools. The system also has something like auto complete so it can lazily expand more complex calls with only valid possible values. Another point is that I expect people to heavily customize their ui, perhaps even per virtual directory, if they aren't primarily using agents
For example I'm going to make a more streamlined one for all the tabular data / SQL capabilities from the video. Kind of like Simonw datasette, but less footguns and servers. Desh makes it hard/impossible to lose data and easy/automatic to track provenance and build data pipelines
That plus the graph ontology layer (adding relations between columns, etc.)
And yes, while it's not exactly hierarchical, the idea is to enable the various interaction modalities (touch, voice, etc.) without much extra effort so accessibility isn't bolted on