Hi Morris, 'El transcluder' ...giggles.
To the topic... I am not sure that there is a need for any special conventions of sorts... other than the most basic idea of what transclusion is or does ...unless you wanted to build some transclusion-functions-library-or-framework around the concept of it, e.g. some tiddler named MyTransclusionCollection containing... !getA <<tiddler ... !!doBeee <<tiddler... !someHTML <html>foo</html> !standardOut $1$2$3$4$5$6$7$8$9 !someInlineScript can't do it in google groups ;-) !!!!!etc pp So, I think, this is rather a matter of taste and whatever it is that you want to achieve with transclusion. In other words, I don't see some special need of specification other than explaining in the __most basic__ terms what transclusion is. So maybe it's less of an exercise to hard-wire the idea of it, but instead to list all of what you possibly can do with it... like in the examples above. As for meaningful abstractions of codebits into standardized chunks... that's not just an issue with transclusion, but - I guess - rather your everyday struggle of what goes into where and possibly into what is called 'the core'. Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=.
