Saddly this is just a speculative fictional idea for how a new Smalltalk could look. Not a real working Smalltalk. And this particular part of the sketch hasn't been filled in.
I think Smalltalk is a wonderful ideal, the combination of simple, powerful and elegant language, with the live world is something we really need.
But I believe it needs to move beyond the specific environment that it inherited from the early researchers.
Obviously the WIMP environment has been historically very important, but it is somewhat old-fashioned now, and not quite what you want today. When I look at Morphic etc. I feel that they’re cluttered with a lot of historical cruft I really don’t want to have to deal with. The live environment should be much more in the direction of something like JuPyter Notebook. Or perhaps more like a spreadsheets, chat streams, web-page etc. More constrained / streamlined to the device / working environments we care about : browsers, tablets, phones and servers.
Yes, have the whole goodness of a dynamic language, live objects etc. Yes, have the source code viewable and editable. But clean out the historical baggage that every Smalltalk implements by default just because it's already there.
Get rid of multiple overlapping windows, and have a single clean “page” with “sections”. Have pages organized into “projects”. Get rid of all those weird Morphic control handles and icons. Is “rotate this” such an important command that every screen object needs to make it a first class “menu” item?
A “notebook” metaphor would be great for documenting / programming “literately”.
Turn the “class browser” into something more like a good contemporary editor. It’s wonderful that the whole of Smalltalk is available to inspect and edit within the class browser. But the class-browser’s navigation / findability etc. are awful. We can do much better in terms of the “information architecture” of a tool to browse, edit and manage the whole system. Look at GitHub or CodePen. Even JavaDoc is nicer is nicer to navigate around.