On Mon, 27 Jun 2011, PMario wrote:
Which IMO is ok for now, but if you want to have some automatic update in the future and you want to reuse some of the TW refresh code, the <span tiddler="ptest1.a" refresh="content"> becomes important.
Ah, okay, I get it now. I couldn't tell what the problems were from your earlier messages. Yes, that would be a problem if some kind of refresh mechanism were being used. However, if such things were needed then there are quite a few other issues that would show up. For example, strictly speaking a <span> may only contain inline elements, not block elements, so shouldn't be used to indicate a transclusion at all...
PS: I have to say, that I wanted to use your code inside TW and it deffinitely causes a refresh problem there, if you change ptest1.a. I thouhgt I point it out, because if you think about some automatic notification if content changes, it may be a problem. A future problem, but a problem q;-)
Yes, inside a tiddlywiki I would think that it would be far better to fix the formatter than do what I'm doing for purpleater. If/when the formatter creates good HTML lots of interesting things wil be possible. For the time being, though, for the task I'm trying to do, I'm trying to work with the data that's given... -- Chris Dent http://burningchrome.com/ [...] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
