OK, MX5 announced yesterday: https://clojurians.slack.com/archives/C06MAR553/p1679672683486079 Next, I figured out (I think) how to provide sth pedagogical. No special effort on a tutorial or doc. Instead, I am creating a new "workshop" repo that will start out with all the quickstart code. • So the workshop starts out with a hefty target (fun). • Then I clean up the quickstart control code, which I treated as pure throwaway at first. Much fun to be had here refactoring, which will incidentally point out how easy is refactoring. • Brave plan is to push tagged commits daily, at the same time updating a project wiki refactoring journal to discuss each tag; • Code will be commented with instructional intent; and... • ....comments will be superseded whenever necessary, so they stay current but require learners to work tag-by-tag if really interested in the app evolution. Once I have the workshop set up, w/mx gets announced.
Forgot to add that once I get the quickstart controller cleaned up, showing off the ease of refactoring, I get to have some fun and do the inspector. The necessary reflection will actually get into MX/WMX internals rather swiftly. Still not sure it will be a useful development tool, but it will be dazzling, as https://youtu.be/6t02Dbp3xsU?t=473 go.