Works in Progress

For the last few days I’ve been looking at the amazing Codestrates project, a development from Webstrates that has been under development by Clemens Klokmose and his team at CAVI since 2015. This has always been a close sibling project since the days of our 2016 paper and the development into Codestrates with its powerful in-browser IDE makes the convergence even more interesting. Reuse and abstractions in Substrates There has always been a fundamental difference in philosophy between Webstrates and Infusion, in that the substrate underlying Webstrates is simply the DOM itself. [Read More]

Reimplementing Infusion for its reactive version made me vow to concentrate on its everyday, bread and butter features at the expense of what might have been “speculative nonsense” in its earlier history. However, implementing something pretty basic – the ability to render lists of components – brought me right back to an old conversation. Here’s the situation – one author wrote a todoItem which is a templateViewComponent: fluid.def("fluid.tests.todoItem", { $layers: "fluid. [Read More]

Trying to put into practice thoughts from the previous two postings on template thinking and weird attributes for event binding revealed some interesting problems. Firing up ${ }-based templates revealed an awkward problem. This prevents us using backtick template literals in code since these automatically interpret ${} syntax and so will break as soon as they are evaluated. At the same time, use of @click style event binding revealed a really interesting limitation. [Read More]

OK, so we have now imported a visually reasonable and properly lithified version of Pell into a tiny static page which is itself lithified from the rendered output of the substrates page, which will be where the most basic editing demo gets scaffolded. I mused about making the disclosing tool into a pencil of the kind we see in the Lively Kernel UI but the “magic wand” was hard to resist and fits in with some rhetoric about this gesture. [Read More]

I get to staring at the markup templates that were already implemented for the Galiano 2023 Bioblitz and thinking how to adapt/reuse them for the upcoming Diatoms of the Salish Sea viz forces me to put some things in focus about how templating is going to have to work for these communities. I’d vaguely hoped that the details of how Infusion templating was going to interact with Hugo templating would somehow just “come out in the wash” but naturally this isn’t going to happen without some kind of focused plan! [Read More]

The substrate’s transition to editability will need to present a “mostly rendered” view of itself – managed by some form of rich text editor. A huge “grab-bag list” is at JefMari’s curated list of Awesome Wysiwyg Editors which can rapidly be whittled down to a shortlist. CKEditor 5 and TinyMCE are familiar from decades ago. But the gold standard is clearly Marijn’s ProseMirror – basic example here and really nice markdown editing example here. [Read More]