Re: [twdev] Help from Web Developer - iframe interaction

2019-02-16 Thread TonyM
Jeremy, I can see having subWikis, may be part of the answer but critical to many of the ideas I suggested is they are interactive, thus I favor your idea of somehow removing the iframe from the refresh tree. Could it be so simple as tagging a tiddler to be "ignored" (no need to explain why not

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-16 Thread Jeremy Ruston
Hi Tony Good stuff! The fundamental issue that would prevent most of those applications working today is that innerwikis are volatile: if the tiddler containing an innerwiki gets actively refreshed then the innerwiki will be deleted and recreated. I think that the only way to get around that w

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-15 Thread TonyM
Jeremy, I have identified some scenarios for embedded iframes, even the innerwiki plugin, I will share, as suggested by you. Please forgive me for my rampant imagination, these ideas come from real life challenges. Given, a Parent wiki, even a single file wiki can spawn an innerwiki with a s

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-12 Thread @TiddlyTweeter
Jeremy Ruston wrote: > > ... we'll need some clear scenarios first. > A lot of my time is spent replicating in TW what Firefox did via Add-Ons before the apocalypse. --- A case would be a matrix of two wiki in iframes side by side you might d-n-d between? --- Another case might be having frame

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-12 Thread Jeremy Ruston
Hi Tony It's good to broaden the understanding of the benefits and pitfalls of iframes. One takeaway from this thread is that using iframes is a well understood technique in the developer community, and TW already uses them in several roles (plugin library, viewing HTML tiddlers, innerwiki, Twe

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-11 Thread TonyM
Jeremy, Thanks for your response. 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 tha

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-11 Thread Jeremy Ruston
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 t

Re: [twdev] Help from Web Developer - iframe interaction

2019-02-10 Thread TonyM
Jeremy, Is this mechanism available from a widget or macro to send to or receive messages as highlighted? 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 als

Re: [twdev] Help from Web Developer - iframe interaction

2019-01-26 Thread TonyM
Jeremy, That is exciting to know. I will look into it, but it may be beyond my current skill set. I appreciate the federation approach and the servers but here I am keen to get single file/single file interaction, especially when single file can be so easy to publish. Perhaps some generic tool

Re: [twdev] Help from Web Developer - iframe interaction

2019-01-26 Thread Jeremy Ruston
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, asynch

[twdev] Help from Web Developer - iframe interaction

2019-01-25 Thread TonyM
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