Mat I have started doing something similar where I have a config tiddler who's value I can change but golbal macros that use the value in there definition, effectively providing a variable that matches the config tiddlers value. This allows one to avoid state tiddlers or config tiddler names being coded which is easy to read and can be locally overridden with a new set widget and the same variable name, if desired without changing the config tiddler.
As I read your suggestion you want to be able to alter the parameters as well. To be of practical use the two transclusions in your example will need to be related because one defines the parameters the second uses the parameters. You could already create a button that adds a tiddler tagged as a macro with the text constructed from your transclusions into a macro definition. The newly defined macro is immediately available for use anywhere in the wiki. You can see here that a lot is possible already but to achieve it you must have a trigger to do it. In this case a button. Hence my desire to add actions to existing core buttons and the on open tiddler navigation. You could get your dynamic macro definition to be triggered by one of the existing buttons so you do not need a separate trigger. An example may be on opening a project tiddler set a current project macro equal to that tiddlers project name. On closing reset it. This would allow you to write project handling tiddlers that respond to the current tiddler. Regards Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/671ebeea-8f00-4ad7-b258-61aa61856ac2%40googlegroups.com.
