I was doing a few things today that I'm not going to blog about, and I decided that I want to start laying the groundwork for putting the Fragment API into MOTR.
I got started pretty late, so in practice, this just meant adding a file to source control that I'm going to transcribe the prototype code into.
Here's the steps to move forward:
- Sketch out the desired interface (going to need the ability to create literal stretches, functions that do not generate an Output, and functions that generate exactly an Output; this division will lock in some choices on the interface side, and simplify implementation; also going to need to make sure the composition operators I prototyped are in there)
- Get all those interfaces into the file I wrote. Due to the high level of coupling in the implementations, I'm not going to try to separate things out just yet.
- Pull in some of the foundational code I've been prototyping in the motrfile. I'm not yet sure where it goes.
- Create the data required to generate the current content of the configuration file, more or less.
One thing I've been punting on is figuring out how to coordinate the naming of the virtualenv. Because some of the parameters should change the requirements, which means they need a custom environment... Maybe the environment names need to be formed from segments associated with the requirements sets... Or something?
Anyway, it's late, and I don't want to dawdle any more.