Hi Tony > Jeremy, > > Is this mechanism available from a widget or macro to send to or receive > messages as highlighted?
No. The only iframe stuff that is implemented at the moment is the plugin library support. To explore further will require JavaScript development. > The "send to" may be the minimum needed as when constructing a HTML page we > can easily add the javascript, but if it were available as both send and > receive within TiddlyWiki users may also be able to use this possibility? It > would be understandable that it were a plugin if the support is not already > built in due to the plugin library. I don't quite follow the question. The communication used by the plugin library is bidirectional, if that's what you mean. > Is the Data widget in innerwiki effectively like this? No, the way it works is that the data widget is completely passive; it doesn't do anything except collect its attributes and render its children. Other widgets that contain those data widgets can process each one, extracting the attributes. Best wishes Jeremy > > Regards > Tony > >> On Sunday, January 27, 2019 at 4:23:38 AM UTC+11, Jeremy Ruston wrote: >> Hi Tony >> >> Browsers support a mechanism to pass messages between a page and the content >> of an iframe that it hosts: >> >> https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage >> >> It’s pretty magical: it allows rich, asynchronous structured communication, >> and is widely supported on all browsers. Best of all, it doesn’t require the >> HTML files to be hosted on the same domain, as is required for XMLHttpRequst. >> >> It’s actually the mechanism that drives the plugin library in TiddlyWiki 5. >> Loading the plugin library means loading an HTML file into an iframe and >> then using window.postMessage to ask it for a particular plugin. >> >> Jed built on the same mechanism to make the Twederation prototypes. >> >> Best wishes >> >> Jeremy >> >>> On 26 Jan 2019, at 02:02, TonyM <[email protected]> wrote: >>> >>> Another Question Arising. >>> >>> When an Iframe is opened in Tiddlywiki, what is rendered becomes "static" >>> that is it will not be rerenderewd if the underlying html file is changes. >>> Is there a method to ask for this to detect a change and reload? >>> >>> Regards >>> Tony >>> >>> >>>> On Saturday, January 26, 2019 at 12:18:14 PM UTC+11, TonyM wrote: >>>> Folks, >>>> >>>> I had a hunch I could go further with HTML Javascript integration. But I >>>> need some help getting some interaction from or between items in an iframe. >>>> >>>> If I place another tiddlywiki in an iframe I can drag and drop between >>>> both the current Wiki and the Iframe tiddlywiki. >>>> >>>> Further to this I have have a html javascript solution in an iframe and I >>>> can use this to see the result and interact with this html java script. >>>> All good so far. >>>> The iframe can appear to be inside the tiddlywiki when in fact it is not >>>> really, so I could use this as a method to show HTTP PUT and GET forms >>>> etc... >>>> >>>> I can also use raw markup to "include" external files. >>>> >>>> My Question to the tiddlywiki aware webDeveloper is what methods are >>>> available for me to improve the interaction between my html javascript in >>>> an iframe? >>>> >>>> I can copy and Past, I can open in new window and print, but are there >>>> other ways of increasing the interaction such as a button to capture the >>>> content currently displayed in the/an iframe designed for data transfer, >>>> or somehow post something into a field or html id in the iframe ? >>>> Another path may be generating json, csv or tid files in the external >>>> javascript/html then provide a button to import that into the wiki. >>>> Perhaps even image selection or generation. >>>> I am also interested in providing php solutions in an iframe but want to >>>> establish how to integrate this with tiddlywiki. >>>> >>>> Special advantages? >>>> Even on a read only wiki's plenty of read/update solutions could be >>>> developed using tried and tested web services >>>> On a NoteSelf or Read Update wiki the results can be "imported" into the >>>> users "version" from what ever services are presented in the iframe. >>>> >>>> The more detailed you suggestions I suppose the better but do not hesitate >>>> to provide answers without too much detail as I simply need a starting >>>> point at present. >>>> >>>> Thanks in advance >>>> Tony >>>> >>>> >>>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/tiddlywikidev/fa02b552-1c0a-49eb-93c5-a87ce85c9b28%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/9550702d-caf3-4131-a93e-66eee593ef21%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/B2F471AD-57AB-4647-AEBB-587B04DAD178%40gmail.com. For more options, visit https://groups.google.com/d/optout.
