/
Conversation with Clemens Klokmose 26-08-15
Conversation with Clemens Klokmose 26-08-15
A "pre- and post-transcript" of discussion between Colin, Antranig and Clemens.
Coloration:
Antranig
Clemens
- CodeMirror treats the DOM as an ephemeral view. Webstrates' DOM is persistent. I might be able to adapt CodeMirror to reestablish it self based on its stored view in the DOM.
- I must admit I haven't completely understood the ProseMirror sync algorithm, but was struck by its focus on relatively flat text with some markup as data model
- I believe the concept of Views have faded into the background. They are just an object representing another object. So my thinking is much more aligned with your ideas now.
- What we do have (suggested by Clayton some time ago) was the concept of a "materialization strategy" (which, when run in reverse, might be considered a "dematerialisation strategy). That is, this is what occurs when "model material" needs to be imaged into some external material (substance!) - which might be a database but even a "view" as traditionally conceived (the DOM). "Dematerialisation" might correspond to "instruments" - e.g. the stream of activities corresponding to mouse clicks needs to be transduced down into a stream of state. Our current challenge is to cast component configuration for the system itself as a "materialisation strategy" - then the system will be able to close upon itself as a self-contained declarative system (given components can themselves house transform and relay rules etc.)
- I like this. Although I am not sure about materialisation/dematerialisation as it seems to imply that the stuff in the computer isn't material.
- Yes, that is a very good point. It's hard really to account for what is "more material" or "less material" than another thing... but ideally we want the stuff "inside" the materialisation boundary to behave more similarly to stuff "on the outside" so ultimately the relationship, one hopes, would become a more symmetric one. Each person, I imagine, on seeing stuff being imported from the other side of the boundary might consider that it has been "materialised".
- Is Michel still pursuing "instumental interaction"?
- Excellent! DATA ORIENTATION with NODES and FACETS... we have wanted some good, shared names for a while (have tried to refer to "STATE ORIENTED PROGRAMMING" which has not really been intelligible)
- Brilliant!
- We didn't get to this in call 1
- Possible to create relays that is only active under certain conditions? E.g. for doing interactive stuff. "When the mouse cursor intersects and object create a relay [of something] until it doesn't intersect anymore"
, multiple selections available,
Related content
Community Workshop Topics from 2014
Community Workshop Topics from 2014
More like this
Community Workshop Topics from 2012
Community Workshop Topics from 2012
More like this
Community Workshop Topics from 2011
Community Workshop Topics from 2011
More like this
Community Workshop and Design Crit Topics from 2017
Community Workshop and Design Crit Topics from 2017
More like this
Community Workshop and Design Crit Topics from 2021
Community Workshop and Design Crit Topics from 2021
More like this
Community Workshop and Design Crit Topics from 2019
Community Workshop and Design Crit Topics from 2019
More like this