Jeremy, While you are focused on this idea.
I can see using an innerwiki to generate or import test data that could be tested against the outer wiki with no permanent impact. No need to make wiki copies, and quick retesting after outer wiki is modified. On a related matter to innerwikis Would it be possible for us to inject tiddlywiki data into an iframe around a html javascript page and get some results back? Such html javascript could be designed to do things we cant do in tiddlywiki like tw5 dom insensitive javascript tools and functions, or even php auth, database queries and more. If these could appear to be in tiddlywiki but are not we could speed the inclusion of a lot of other open source solutions - perhaps discord, image conversion tools, svg design tools and more. I am possibly taking this too far, but what if these "seperate" pages are actualy served from tiddly server, tiddlers from the outer wiki, like the single tiddlers view can be served? Like innerwikis, these would be "inner pages". This would help us "script kiddies" and provide rapid intergrations perhaps even openid auth. 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/4693096d-8bb7-4fcc-9bad-b235d81bc25e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
