Pretty close. This is somewhat close, but I don’t really get this "caching" thing. I thought that every page has it’s own set of TV’s instantiated on page creation and remembering any chances on PAGE scope, not global SCOPE.
If I can get from Snippet a TV of template the Snippet resides in, then I will be able to develop some kind of functionality I want. Not that complex as I wanted previously. With some additional effort I could indeed (If my assumptions are correct) even develop something like paragraphsystem, but that would require substantial more TV’s for each template.
splittingred - YES, that looks like a simplified parapgraph system idea, thank you!. With some extensions for ordering, that would be what I was thinking of.
Combining this with having Component (well, Snippet+Chunk) properties hardcoded into template in form of grouped TV’s that will make a complete solution for me. I would like some experienced developer to confirm if my way of thinking (of the solution) fits into MODx design.
Well, pachinko, I understood it the same way, that article was helpful also. The idea is that if you cannot have properties in Components, lets put them as TV’s in template that steer those Components. This solution has some limitations, but will be sufficient in 70% of my cases.
In the future, it would be cool to have properties assigned to Snippets, just the same way as they are bound to template now. I can see this as another secion in the page edit, which will basically iterate through every snippet, read their properties and allow to edit them. Just a thought.