04:27 <seangrove> dsheets: I'm trying to get a layout directive working (just exploring in my own branch), and I have both the layout file and the post parsed in memory, but having a bit of trouble figuring out how to insert one blueprint document inside of another. How would you recommend I go about it? Getting it into the right point is important, and so making it a hole would work for that, but require another pass through with the new document (plus

04:27 <seangrove> the mutative nature is making stuff like that more difficult).

04:30 <seangrove> I know you're pretty busy now though, so no worries if nothing simple to explain comes to mind

12:35 <dsheets> seangrove, hi, I'm a bit fuzzy on the template variable interfaces you have. if you want to put a blueprint into another, you should be able to just insert the inner document into the bindings used by the outer document. Then, when the template is rendered, your inner document will be inserted into the outer.

12:37 <dsheets> If there is no hole in the outer document, then either a way to parse it with holes in place is required or we need to develop a pattern scanning system (not yet, probably). If you want the binding to be immutable, we don't have a solution yet but whatever the answer is would fit into the design stuff we were talking about.

12:38 <dsheets> A major component of the scope design is what happens to the hole-namespace of the inner document. Is it exposed directly at the outer layer? What if there are name conflicts? How do we handle those now? Should it be namespaced with dots?

15:01 <seangrove> dsheets: Yeah, because I'm not sure about all of that, I've been building small things in jekyll, and getting Tower (hackily) to the point where it can render it the same way (albeit it <t:include ...> tags instead of {% include ... %} for now). I want to 1.) use this things asap, and 2.) have a better sense of how the pieces should compose before inflicting a bad design on others

15:02 <dsheets> seangrove, yep, sounds like you're on the right track

15:03 <dsheets> getting it usable for *someone* asap is a good idea :-)