Tobias Beer wrote: > > So, yes, it sounds like there might be ways to do *manual* communication, >
In your communication description it looks like A and B must go look to see if there are messages for them. But in the their demo <http://mattsnider.com/hash-hack-for-cross-domain-iframe-communication/>it does appear to be push, into the other iframe, after all (...or?) because the receiving iframe is set to listen as per: HashHack.onMessage(function(e) { // message is stored on e.data console.log(e.data); }); Pretty much the way I would imagine an emailbox does, no? Regarding your tiddlyspot test: I'm a bit surprised we don't get to see any contents in the iframed iframe. BTW, I wonder if iframes are made so to stop the loop already after "iframing the iframe". Do you know if there is any way to specify an identity of specific tiddlers so the iframe really could display only that tiddler? I cannot find any identifier by "inspecting the element". Also not for the river, wihch would cut out the sidebar and actually be very handy to get multiple tiddlers at once (for when url includes a filter). As an option to iframes, there is maybe _canonical_uri_ object frame (if that is the term). I got this from a TW by Andrew Harrison: \define objfra() <object type="text/html" data="$(path)$" class="tc-object-frame"></object> <<objfra>> This would of course make my initial post about the url trick not relevant... I think. <:-) -- 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.
