Hi Mat, > On a need basis perhaps? I.e if a part can be reused, then it is > tiddlified to avoid redundance in the system. Not sure how to deal with if > there's later a wish to change it in one context but not the other. Or > maybe clone+change is obvoius solution? >
Yes, but that introduces a few questions, like... - What name should that new tiddler get? - Does it need tagging? - Any fields? - Where do I need to link it? - How do I put it into context? - Does it need ordering in some list? - etc... Whereas I could simply do some section magic <https://groups.google.com/forum/#!topic/tiddlywiki/23PzU2qCsj4>, reference that bit form anywhere, have it neatly displayed in a clickable toc... and all those things that make not really big tiddlers not nessessarily smaller than they have to be. Let me put it slightly differently: there is a too small... in the sense of: "smaller than is perhaps good for ya"... omg, all the uncertainty that comes with the quantum-approach to anything. ^^ Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
