Hi Tony I don't think these ideas are related to the innerwiki plugin so much as the underlying iframe primitive. Generally, there has been extensive exploration of using iframes as a means of integration in the browser; and iframes are widely used for advertisements and for embedded widgets, and hence the techniques you're interested in exploring are pretty widely documented/understood.
Generally speaking, though, integration via iframes is inferior to integration via the server. If you've got a server available, then things like handing off to a PHP login script in a separate window are pretty trivial without needing iframes. Iframes really shine when one doesn't have the option of a server. Anyhow, via the experimental single tiddler view, the server already has the ability to host self-contained HTML apps as single tiddlers. And ordinary wikitext can freely create iframes and inject content into them, so I think you can experiment along the lines you describe. Best wishes Jeremy. > I am suggesting what If I have a plain text tiddler, that contains a HTML > page including head and body, javascript, including libraries etc... The kind > of thing I may find available in a javascript library for special features or > a nice landing page layout (It is not used for anything in the parent). It is > merely stored in the parent wiki. Lets us call it the HTML-Tool ,Then we > could do one of two things; > > Present the HTML-Tool at an address such as https:/hostname.com/tiddlername > similar to the single Tiddler view, but simply deliver it, as it is, to the > browser, as if it were a standalone html+ file. > Generate an Inner (perhaps not innerwiki but innerhtml or innerpage) that is > an iframe to the aforementioned HTML-Tool without any Tiddlywiki just > rendered as in the first case. > In both circumstances it would be nice if some rudimentary string could be > passed to and from such HTML-Tool, perhaps that looks like a json tiddler in > the parent wiki, and json file in the HTML-Tool? > > It is in someways taking the single file concept further allowing tiddlywiki > to host other content in its server, a bit like the 5.1.18 feature Adds > support for serving static file attachments over HTTP) > > I could see myself hosting in my TiddlyWiki a html page that lets people > register as a member in my wordpress member site. No need to manage a > separate file, it lives in my wiki, but is served by the tiddlywiki server. > > Regards > 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/723001cf-e95e-4ecb-a853-04fa3f96db45%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/737D3648-103D-4043-8881-A82F32615EE2%40gmail.com. For more options, visit https://groups.google.com/d/optout.
