matrix

kennytilton 2023-03-05T18:11:24.998489Z

Damn, I ended up at eight. 🙂 https://kennytilton.github.io/web-mx-quickstart/ Getting fancy with the glossary! OK, that's been beaten to death. But feedback still welcome! Closing in on an official announcement....

phronmophobic 2023-03-05T22:02:40.392439Z

Looks great! For my monitor size, each section is taller than my monitor. So when I hit next at the bottom of a doc, the next section shows up, but I'm now at the bottom of the next section instead of the top and need to scroll up. Not a huge deal. In general, I tend to prefer long scrollable docs with sections rather than individual "pages". It makes it much easier to Ctrl+F and search the doc when I want to look something up. I also noticed that you can't link to individual sections which is generally useful and good for SEO. It might be useful to add #header-fragments in the URL when you navigate to each of the sections.

kennytilton 2023-03-05T22:36:20.653079Z

Thx, @smith.adriane! Agreed on the scrolling ugliness. I tried stopPropagation. I'll try preventDefault. As for linking to individual sections, I almost added routing support, and will do that since you picked up on it. Right now there is no URL, it's just a formula deciding to swap in new DOM for a container. CTRL+F is tougher. Maybe I should do a search capability? The thing is, like a dumbass I never intended this quickstart to be a showcase example, but of course it is since I mean this to be the entry point! But I think the real hook will be somehow conveying how cool/easy it is programming this way, and I am anxious to get on with that. I suppose the cool/easy could be demonstrated in the context of enhancing the quickstart, but I am also considering building a graphical w/mx inspector, including nifty SVG to display the DAG alongside a running w/mx app. Hmm, maybe the cool/easy will be the inspector with QS as the inspectee. 🤔

phronmophobic 2023-03-05T22:57:59.706599Z

I think most of these problems go away if all the docs are in one long scrollable document (eg, https://book.clerk.vision/#plotly). Obviously, everyone has their preferences. Just wanted to share a perspective in case it was helpful. There's always more than one way to go about it.

kennytilton 2023-03-05T23:11:59.203779Z

You know, this is great. I needed a decent example of wrapping a third-party library for the QS, and bide will be perfect, not too labor intensive, but not too trivial. And I already have the code in my TodoMVC implementation. Oh, and I just remembered scrollTo, might be simplest. That clerk example is great! Maybe when I get to the w/mx reference I will emulate that. Thx for the idea! 🙏