On May 3, 2016 12:04 AM, "Marius Kintel" <marius@kintel.net> wrote: > We need a way of making the values from the customizer available for rendering. I’m not sure how teepee solved that in his prototype branch, but this could be part of the evaluator (the component which transforms the AST to a CSG Tree). > Alternatively, we could modify the AST directly, by injecting the values back into the AST. I’m not sure what the best solution would be. It might be beneficial to app design to keep the AST read-only for subsequent processes, and thus merge customizer values during evaluation, but it’s a bit early to say. I think teepee used the alternative method thats why I asked regarding it. As I way also thinking in that way. so, I didn't found any need to make changes regarding evaluator. So, we have two choices here also :) . -- Amarjeet Singh https://amarjeetkapoor1.wordpress.com https://github.com/amarjeetkapoor1 https://bitbucket.org/amarjeetkapoor " There are things and there are pointers to the things. "