On Nov 21, 10:43 pm, Tobias Beer <[email protected]> wrote: > Hi Morris, > > 'El transcluder' ...giggles.
This depends on the the finesse of El Transcluder and the attitude of La Transcludee ;-) In this rather vague description below of which I have transdelivered (it is certainly not transquotation as described below) is not very enlightening. Ref: http://en.wikipedia.org/wiki/Transclusion "Nelson defines transclusion as "the same content knowably in more than one place", setting it apart from more special cases such as the inclusion of content stored in a different location (which he calls "transdelivery") or "explicit quotation which remains connected to its origins" (which he calls "transquotation"). I am only talking about client-side. The methods I have been using requires better definition. By using a script to manipulate information from possibly several different places, drawing with it things such as tiddler titles, tiddler tags, and the tiddler content itself; then manipulating and enhancing it in some way, then delivering it to another tiddler which in turn becomes another function altogether requires some naming convention for the component parts. > ...unless you wanted to build some > transclusion-functions-library-or-framework around the concept of it, > e.g. some tiddler named MyTransclusionCollection I think that's what I'm getting at. I have constructed such a library in an ad hoc way and now I'd like to give it structure. What I described above could probably be called 'mashup'; but that's rather too common, or the people who use it may be anyhow :-) I would like these names to have dignity. Perhaps I could call it jClusion. As one day it may have to be considerd for inclusion (no pun intended) in the core. I'm thinking transclusion is the end result, something that directs the action the 'transcluder' and the result as the 'transcluded' Trans... as a prefix is rich with a multitude of options so one shouldn't become too transfixed with it lest we transform this exercise into a 'misclusion' which I am thinking I will make it a reserved word for trancluded errors. I think I'll work on it, any suggestions or contributions are welcome... Morris On Nov 21, 10:43 pm, Tobias Beer <[email protected]> wrote: > 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=.
